RationalBloks

List all your RationalBloks projects with their status and URLs

{
  "type": "object",
  "properties": {},
  "required": []
}

Get detailed information about a specific project

{
  "type": "object",
  "properties": {
    "project_id": {
      "type": "string",
      "description": "Project ID (UUID)"
    }
  },
  "required": [
    "project_id"
  ]
}

Get the JSON schema definition of a project in FLAT format. Returns the schema structure where each table name maps directly to field definitions. This is the same format required for create_project and update_schema. USE CASES: Review current schema before making updates, copy schema as template for new projects, verify schema structure after deployment, learn the correct schema format by example. The returned schema will be in FLAT format: {table_name: {field_name: {type, properties}}}. The response also says whether this saved schema is the deployed one: saved_schema_deployed is true when the last deploy applied it, false when it was saved after the last deploy (undeployed_changes then lists what deploying it would change), and null when no deployed schema is on record. A LARGE SCHEMA: pass tables or fields to read only the part you are about to change — the answer's 'version' is the whole schema's either way, so a slice is enough to patch it with patch_schema(expected_version=...).

{
  "type": "object",
  "properties": {
    "project_id": {
      "type": "string",
      "description": "Project ID (UUID)"
    },
    "tables": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Read only these tables, whole (e.g. [\"parameters\"]). A table the schema does not hold is refused."
    },
    "fields": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Read only these fields, each written 'table.field' (e.g. [\"parameters.is_clock\"]); their table's own keys come with them."
    }
  },
  "required": [
    "project_id"
  ]
}

Get information about the authenticated user

{
  "type": "object",
  "properties": {},
  "required": []
}

List your registered BYOC resource pools (client-owned Kubernetes clusters). Each returned cluster has an 'id' you MUST pass as create_project's cluster_id to deploy a project onto your own infrastructure — owned hosting is retired, so every project we operate runs on your own cluster. Registering a pool is a UI action (create a bare Ubuntu box, authorise the key we generate, then we provision it into a cluster automatically) — this tool only lists pools you already registered, it never handles cluster credentials.

{
  "type": "object",
  "properties": {},
  "required": []
}

Check the status of a job (a create, deploy, promotion, rollback or deletion). STATUS VALUES: pending (queued), processing (in progress), completed (success), failed. Call it until the status is completed or failed: every job ends, since a job whose server stopped is failed within about three minutes, and a deploy can take up to 15 minutes. If status is 'failed', read failure_side and error: 'customer' means the project's input is proven the cause (an invalid schema, data the new schema does not fit, a change the resource pool cannot hold), and error says what to change; 'platform' means no input of the project is known to cause it: report it to RationalBloks rather than changing the schema.

{
  "type": "object",
  "properties": {
    "job_id": {
      "type": "string",
      "description": "Job ID returned from deployment operations"
    }
  },
  "required": [
    "job_id"
  ]
}

List a project's jobs, newest first: every create, deploy, promotion, rollback, resource change and module operation, each with its status, error, failure_side and when it started and ended. A job's record is kept for the life of the project, so this is how to find out what an operation did when you no longer have its job_id (after an interruption, or in a later session): the first job of the job_type you want is the latest. Read older jobs a page at a time with offset; a page shorter than limit is the last.

{
  "type": "object",
  "properties": {
    "project_id": {
      "type": "string",
      "description": "Project ID (UUID)"
    },
    "limit": {
      "type": "integer",
      "description": "Max jobs to return (1-1000, default 100)"
    },
    "offset": {
      "type": "integer",
      "description": "Jobs to skip, newest first (default 0)"
    }
  },
  "required": [
    "project_id"
  ]
}

Get detailed project info including deployment status and resource usage. DEPLOYMENT STATUS: Running (healthy), Pending (starting), CrashLoopBackOff (init container failed - usually schema format error), ImagePullBackOff (image build failed). TROUBLESHOOTING: If status is CrashLoopBackOff, the schema is likely in wrong format (nested 'fields' key or missing 'type' properties). Use get_schema to review current schema. If replicas show 0/2, the init container (migration runner) is failing. This is almost always a schema format issue. RETURNS THE LIVE API URL: staging.url and production.url carry the deployed base URL for each environment (append /docs for the interactive OpenAPI docs); github.url is the generated repository. create_project does NOT return a URL, so this is the tool to call once get_job_status reports the deployment finished.

{
  "type": "object",
  "properties": {
    "project_id": {
      "type": "string",
      "description": "Project ID (UUID)"
    }
  },
  "required": [
    "project_id"
  ]
}

Get the deployment and version history (git commits) for a project. Shows all schema changes with commit SHA, timestamp, and message. USE CASES: Review what changed between deployments, find the last working version before issues started, get commit SHA for rollback_project.

{
  "type": "object",
  "properties": {
    "project_id": {
      "type": "string",
      "description": "Project ID (UUID)"
    }
  },
  "required": [
    "project_id"
  ]
}

Get pre-built template schemas for common use cases. ⭐ USE THIS FIRST when creating a new project! Templates show the CORRECT schema format with: proper FLAT structure (no 'fields' nesting), every field has a 'type' property, foreign key relationships configured correctly, best practices for field naming and types. Available templates: Start from Scratch (every field type), Team Collaboration (workspaces, channels, messages, tasks), E-Commerce Store (customer profiles, products, orders and their line items, reviews, shipments). Each entry's 'schema' goes to create_project as is or adapted; its 'tables' notes say how each table is authorized. TIP: Study these templates to understand the correct schema format before creating custom schemas.

{
  "type": "object",
  "properties": {},
  "required": []
}

Get the reference for ADVANCED schema features the templates do not show — read this before adding authorization or derived fields to a schema. Covers: __policy__ (relationship-based read/write authorization with single- and multi-hop membership paths, and the rules that decide whether adopting it is safe — it replaces creator-ownership per table and fails closed on a null link), computed columns (read-only values derived from other columns), __constraints__ (composite uniqueness), __audit__ (append-only audit log), __admin_write__ (a table only admins write), how user foreign keys are attributed on create, and reading many rows in one request with <field>__in=a,b,c (the values separated by commas only).

{
  "type": "object",
  "properties": {},
  "required": []
}

Get your subscription tier, limits, and usage

{
  "type": "object",
  "properties": {},
  "required": []
}

Get resource usage metrics (CPU, memory) for a project

{
  "type": "object",
  "properties": {
    "project_id": {
      "type": "string",
      "description": "Project ID (UUID)"
    }
  },
  "required": [
    "project_id"
  ]
}

Get object-storage usage for a project: file count and bytes used against the plan limits.

{
  "type": "object",
  "properties": {
    "project_id": {
      "type": "string",
      "description": "Project ID (UUID)"
    },
    "environment": {
      "type": "string",
      "description": "Environment: staging or production (default: production)"
    }
  },
  "required": [
    "project_id"
  ]
}

List a project's uploaded files (metadata + public URLs), most recent first. Inspection only — files are not streamed through MCP.

{
  "type": "object",
  "properties": {
    "project_id": {
      "type": "string",
      "description": "Project ID (UUID)"
    },
    "environment": {
      "type": "string",
      "description": "Environment: staging or production (default: production)"
    },
    "limit": {
      "type": "integer",
      "description": "Max files to return (1-1000, default 100)"
    },
    "offset": {
      "type": "integer",
      "description": "Pagination offset (default 0)"
    }
  },
  "required": [
    "project_id"
  ]
}

Get the schema as it was at a specific version/commit

{
  "type": "object",
  "properties": {
    "project_id": {
      "type": "string",
      "description": "Project ID (UUID)"
    },
    "version": {
      "type": "string",
      "description": "Commit SHA of the version"
    }
  },
  "required": [
    "project_id",
    "version"
  ]
}

Create a new RationalBloks project from a JSON schema. ⚠️ CRITICAL RULES - READ BEFORE CREATING SCHEMA: 1. FLAT FORMAT (REQUIRED): ✅ CORRECT: {users: {email: {type: "string", max_length: 255}}} ❌ WRONG: {users: {fields: {email: {type: "string"}}}} DO NOT nest under 'fields' key! 2. FIELD TYPE REQUIREMENTS: • string: MUST have "max_length" (e.g., max_length: 255) • decimal: MUST have "precision" and "scale" (e.g., precision: 10, scale: 2) • datetime: Use "datetime" NOT "timestamp" • ALL fields: MUST have "type" property 3. AUTOMATIC FIELDS (DON'T define): • id (uuid, primary key) • created_at (datetime) • updated_at (datetime) 4. USER AUTHENTICATION: ❌ NEVER create "users", "customers", "employees" tables with email/password ✅ USE built-in app_users table Example: { "employee_profiles": { "user_id": {type: "uuid", foreign_key: "app_users.id", required: true}, "department": {type: "string", max_length: 100} } } 5. AUTHORIZATION: Add user_id → app_users.id to enable "only see your own data" Example: { "orders": { "user_id": {type: "uuid", foreign_key: "app_users.id"}, "total": {type: "decimal", precision: 10, scale: 2} } } 6. FIELD OPTIONS: • required: true/false • unique: true/false • default: any value • enum: ["val1", "val2"] • foreign_key: "table.id" AVAILABLE TYPES: string, text, integer, decimal, boolean, uuid, date, datetime, json, uuid_array, integer_array, text_array, float_array Array types store PostgreSQL native arrays with automatic GIN indexing: • uuid_array: UUID[] — for sets of references (e.g., tensor coordinates) • integer_array: BIGINT[] — for dimension indices, integer sets • text_array: TEXT[] — for tags, categories, label sets • float_array: DOUBLE PRECISION[] — for weight vectors, scores GIN-indexed operators: @> (contains), <@ (contained_by), && (overlaps) BACKEND ENGINE: • python (default): FastAPI backend — mature, full-featured • rust: Axum backend — faster cold starts, lower memory, high performance WORKFLOW: 1. Use get_template_schemas FIRST to see valid examples 2. Create schema following ALL rules above 3. Call this tool (optionally choose backend_type: "python" or "rust") 4. Monitor with get_job_status (2-5 min deployment) After creation, use get_job_status with returned job_id to monitor deployment. While RationalBloks is being updated, the call is refused with 'RationalBloks is being updated': call it again in a few minutes.

{
  "type": "object",
  "properties": {
    "name": {
      "type": "string",
      "description": "Project name"
    },
    "schema": {
      "type": "object",
      "description": "JSON schema in FLAT format (table_name → field_name → properties). Every field MUST have a 'type' property. Use get_template_schemas to see valid examples."
    },
    "backend_type": {
      "type": "string",
      "enum": [
        "python",
        "rust"
      ],
      "description": "Backend engine: 'python' (FastAPI, default) or 'rust' (Axum, faster). Default: python"
    },
    "cluster_id": {
      "type": "string",
      "description": "REQUIRED — BYOC resource pool ID (from list_clusters) to deploy this project onto your own cluster. Owned hosting is retired: a project we operate must run on your own infrastructure. Register a pool via the Resource Pools UI first, then pass its id here."
    }
  },
  "required": [
    "name",
    "schema",
    "cluster_id"
  ]
}

Update a project's schema (saves to database, does NOT deploy). ⚠️ CRITICAL: Follow ALL rules from create_project: • FLAT format (no 'fields' nesting) • string: max_length (default 255) • decimal: precision + scale (default 10, 2) • Use "datetime" NOT "timestamp" • DON'T define: id, created_at, updated_at • NEVER create users/customers/employees tables (use app_users) ⚠️ MIGRATION RULES: • New fields MUST be "required": false OR have "default" value • Cannot add required field without default to existing tables • Safe: {new_field: {type: "string", max_length: 100, required: false}} WORKFLOW: 1. Use get_schema to see current schema 2. Modify following ALL rules 3. (optional) Call update_schema with dry_run=true to preview the migration first 4. Call update_schema (saves only) 5. Call deploy_staging to apply changes 6. Monitor with get_job_status CHANGING PART OF A SCHEMA: use patch_schema. This tool replaces the WHOLE schema, so it is for a new data model or a template; sending back a large schema to change one field risks changing something else on the way. DRY RUN: pass dry_run=true to save nothing and read back 'diff' — every property this schema changes in the saved one, so an accidentally changed description, default, enum or computed case shows up — and 'plan', the migration a deploy would then run, with destructive steps flagged. NOTE: Without dry_run this only saves the schema. You MUST call deploy_staging afterwards to apply changes.

{
  "type": "object",
  "properties": {
    "project_id": {
      "type": "string",
      "description": "Project ID (UUID)"
    },
    "schema": {
      "type": "object",
      "description": "New JSON schema in FLAT format (table_name → field_name → properties). Every field MUST have a 'type' property."
    },
    "dry_run": {
      "type": "boolean",
      "description": "Save nothing: answer the property-level diff against the saved schema and the migration plan a deploy would run."
    },
    "expected_version": {
      "type": "string",
      "description": "The 'version' a get_schema read answered. The save is refused (409) when the saved schema changed since, so two editors never overwrite each other silently."
    }
  },
  "required": [
    "project_id",
    "schema"
  ]
}

Change PART of a project's schema (saves to database, does NOT deploy). Send only the change. The server applies it to the saved schema, in order and all together, and keeps every table and field it does not touch — including their identity, so a rename stays a rename and the column keeps its data. OPERATIONS (each one small object, applied in the order given): • {"op": "add_table", "table": "clocks", "definition": {...}} new table, same FLAT rules as create_project • {"op": "drop_table", "table": "clocks"} • {"op": "rename_table", "table": "clocks", "to": "timers"} • {"op": "add_field", "table": "assets", "field": "serial", "definition": {"type": "string", "max_length": 64}} • {"op": "drop_field", "table": "parameters", "field": "is_clock"} • {"op": "rename_field", "table": "parameters", "field": "is_clock", "to": "clock_kind"} • {"op": "set_field", "table": "assets", "field": "name", "properties": {"max_length": 300}} merges; a property set to null is removed • {"op": "set_table", "table": "assets", "properties": {"__audit__": true}} __policy__, __constraints__, __audit__, __admin_write__ ALL OR NOTHING: an operation that cannot be applied — a table or field that is not there, a name already taken, a schema the deploy would refuse — refuses the whole patch, naming the operation, and nothing is saved. EVERY ANSWER IS A DIFF: 'applied' (what each operation did), 'diff' (every changed property by path), 'summary' and 'plan' (the migration a deploy would then run), and 'version' (the schema's version after the change). You never need to read the whole schema back to see what you did. WORKFLOW: 1. get_schema with tables/fields to read the part you are changing (its 'version' is the whole schema's) 2. patch_schema with dry_run=true: check 'diff' and 'plan' 3. patch_schema with the same operations (pass expected_version to be refused if someone else saved meanwhile) 4. deploy_staging (confirm_destructive=true when the plan drops data), then get_job_status

{
  "type": "object",
  "properties": {
    "project_id": {
      "type": "string",
      "description": "Project ID (UUID)"
    },
    "operations": {
      "type": "array",
      "items": {
        "type": "object"
      },
      "description": "The operations, applied in order and all together. See the tool description for every op and its fields."
    },
    "dry_run": {
      "type": "boolean",
      "description": "Save nothing: answer what the operations did, the diff and the migration plan a deploy would run."
    },
    "expected_version": {
      "type": "string",
      "description": "The 'version' a get_schema read answered. The patch is refused (409) when the saved schema changed since, so two editors never overwrite each other silently."
    }
  },
  "required": [
    "project_id",
    "operations"
  ]
}

Deploy a project to the staging environment. This triggers: (1) Schema validation, (2) Docker image build, (3) GitHub commit, (4) Kubernetes deployment, (5) Database migrations. The operation is ASYNCHRONOUS - it returns immediately with a job_id. Use get_job_status with the job_id to monitor progress. Deployment typically takes 2-5 minutes depending on schema complexity. If deployment fails, read the job's error first: one that starts with 'RationalBloks platform error' is the platform's, not the schema's. Otherwise check: (1) Schema format is FLAT (no 'fields' nesting), (2) Every field has a 'type' property, (3) Foreign keys reference existing tables, (4) No PostgreSQL reserved words in table/field names. Use get_project_info to see if the deployment succeeded. A deploy that drops data is refused until you pass confirm_destructive=true after reviewing the plan. One operation runs on a project at a time: while another runs, the call is refused and the refusal names the running job; wait for it with get_job_status, then call again. While RationalBloks is being updated, the call is refused with 'RationalBloks is being updated': call it again in a few minutes.

{
  "type": "object",
  "properties": {
    "project_id": {
      "type": "string",
      "description": "Project ID (UUID)"
    },
    "confirm_destructive": {
      "type": "boolean",
      "description": "Set true only after reviewing the plan: a deploy that drops tables, columns, entities, relationships or fields is refused without it"
    }
  },
  "required": [
    "project_id"
  ]
}

Promote staging to production (requires paid plan) A deploy that drops data is refused until you pass confirm_destructive=true after reviewing the plan. One operation runs on a project at a time: while another runs, the call is refused and the refusal names the running job; wait for it with get_job_status, then call again. While RationalBloks is being updated, the call is refused with 'RationalBloks is being updated': call it again in a few minutes.

{
  "type": "object",
  "properties": {
    "project_id": {
      "type": "string",
      "description": "Project ID (UUID)"
    },
    "confirm_destructive": {
      "type": "boolean",
      "description": "Set true only after reviewing the plan: a deploy that drops tables, columns, entities, relationships or fields is refused without it"
    }
  },
  "required": [
    "project_id"
  ]
}

Delete a project (removes GitHub repo, K8s deployments, and database). It runs as a job: poll the returned job_id with get_job_status until it is completed. One operation runs on a project at a time: while another runs, the call is refused and the refusal names the running job; wait for it with get_job_status, then call again. While RationalBloks is being updated, the call is refused with 'RationalBloks is being updated': call it again in a few minutes.

{
  "type": "object",
  "properties": {
    "project_id": {
      "type": "string",
      "description": "Project ID (UUID)"
    }
  },
  "required": [
    "project_id"
  ]
}

Rollback a project to a previous version. ⚠️ WARNING: This reverts schema AND code to the specified commit. Database data is NOT rolled back. Use get_version_history to find the commit SHA of the version you want to rollback to. After rollback, use get_job_status to monitor the redeployment. Rollback is useful when a schema change breaks deployment. One operation runs on a project at a time: while another runs, the call is refused and the refusal names the running job; wait for it with get_job_status, then call again. While RationalBloks is being updated, the call is refused with 'RationalBloks is being updated': call it again in a few minutes.

{
  "type": "object",
  "properties": {
    "project_id": {
      "type": "string",
      "description": "Project ID (UUID)"
    },
    "version": {
      "type": "string",
      "description": "Commit SHA or version to rollback to"
    },
    "environment": {
      "type": "string",
      "description": "Environment: staging or production (default: staging)"
    }
  },
  "required": [
    "project_id",
    "version"
  ]
}

Rename a project (changes display name, not project_code)

{
  "type": "object",
  "properties": {
    "project_id": {
      "type": "string",
      "description": "Project ID (UUID)"
    },
    "name": {
      "type": "string",
      "description": "New display name for the project"
    }
  },
  "required": [
    "project_id",
    "name"
  ]
}

Get the graph schema definition of a project. Returns the hierarchical schema with nodes (entities) and relationships. Graph schemas define entity hierarchies and typed relationships — a different format than relational flat-table schemas. The response also says whether this saved schema is the deployed one: saved_schema_deployed is true when the last deploy applied it, false when it was saved after the last deploy (undeployed_changes then lists what deploying it would change), and null when no deployed schema is on record.

{
  "type": "object",
  "properties": {
    "project_id": {
      "type": "string",
      "description": "Project ID (UUID)"
    }
  },
  "required": [
    "project_id"
  ]
}

Get pre-built graph template schemas for common use cases. ⭐ USE THIS FIRST when creating a new graph project! Templates show the CORRECT graph schema format with: proper node definitions (description, flat_labels, schema with flat field definitions), relationship configurations (from, to, cardinality, data_schema), and hierarchical entity nesting. Available templates: Start from Scratch (hierarchy, flat labels, every field type), Social Network (people, organizations, content, follows), Knowledge Graph (topic hierarchy, articles, authors, concepts), Product Catalog (products, categories, suppliers, reviews). Each entry's 'schema' goes to create_graph_project as is or adapted. TIP: Study these templates to understand the correct graph schema format before creating custom schemas.

{
  "type": "object",
  "properties": {},
  "required": []
}

Get the deployment and version history for a graph project. Shows all schema changes with commit SHAs, timestamps, version numbers, and messages. Use this to find a specific version for rollback operations.

{
  "type": "object",
  "properties": {
    "project_id": {
      "type": "string",
      "description": "Project ID (UUID)"
    }
  },
  "required": [
    "project_id"
  ]
}

Get the graph schema as it existed at a specific version/commit. Use get_graph_version_history to find commit SHAs. Useful for comparing schemas across versions or auditing changes.

{
  "type": "object",
  "properties": {
    "project_id": {
      "type": "string",
      "description": "Project ID (UUID)"
    },
    "version": {
      "type": "string",
      "description": "Commit SHA of the version to retrieve"
    }
  },
  "required": [
    "project_id",
    "version"
  ]
}

Get detailed graph project information including Kubernetes deployment status, Neo4j database health, pod status, and resource usage. Use this after deployment to verify the graph project is running correctly.

{
  "type": "object",
  "properties": {
    "project_id": {
      "type": "string",
      "description": "Project ID (UUID)"
    }
  },
  "required": [
    "project_id"
  ]
}

Create a new Neo4j graph database project from a hierarchical JSON schema. ⚠️ GRAPH SCHEMA FORMAT — READ BEFORE CREATING: Graph schemas define nodes (entities) and relationships, NOT flat database tables. Each field is a dict with "type" and optional "required": true (defaults to false). SCHEMA STRUCTURE: { "nodes": { "EntityName": { "description": "What this entity represents", "flat_labels": ["AdditionalLabel"], "schema": { "field_name": {"type": "string", "required": true}, "other_field": {"type": "integer"} } } }, "relationships": { "RELATIONSHIP_TYPE": { "from": "EntityName", "to": "OtherEntity", "cardinality": "MANY_TO_MANY", "data_schema": { "field_name": {"type": "date"} } } } } FIELD TYPES: string, integer, float, boolean, date, json CARDINALITY OPTIONS: ONE_TO_ONE, ONE_TO_MANY, MANY_TO_ONE, MANY_TO_MANY HIERARCHICAL NODES: Nest entities inside parent entities to create type hierarchies. Child entities inherit parent labels automatically. Example: { "nodes": { "Animal": { "description": "Base animal entity", "flat_labels": ["LivingThing"], "schema": { "name": {"type": "string", "required": true}, "habitat": {"type": "string"} }, "Dog": { "description": "A dog (inherits Animal labels)", "flat_labels": ["Pet"], "schema": { "breed": {"type": "string", "required": true}, "trained": {"type": "boolean"} } } } }, "relationships": { "OWNS": { "from": "Person", "to": "Animal", "cardinality": "ONE_TO_MANY" } } } RULES: 1. "nodes" key is REQUIRED — must contain at least one entity 2. Each entity needs "description" and "schema" with field definitions 3. Each field is {"type": "...", "required": true/false} — required defaults to false 4. Relationship "from"/"to" must reference defined node names 5. Relationship types should be UPPER_SNAKE_CASE 6. Entity names should be PascalCase 7. Automatic fields (id, created_at, updated_at) are NOT needed 8. Use get_graph_template_schemas FIRST to see valid examples WORKFLOW: 1. Use get_graph_template_schemas to see valid examples 2. Create schema following the rules above 3. Call this tool 4. Monitor with get_job_status (2-5 min deployment) After creation, use get_job_status with returned job_id to monitor deployment. While RationalBloks is being updated, the call is refused with 'RationalBloks is being updated': call it again in a few minutes.

{
  "type": "object",
  "properties": {
    "name": {
      "type": "string",
      "description": "Project name"
    },
    "schema": {
      "type": "object",
      "description": "Graph schema with 'nodes' and optionally 'relationships' keys. Use get_graph_template_schemas to see valid examples."
    },
    "cluster_id": {
      "type": "string",
      "description": "REQUIRED — BYOC resource pool ID (from list_clusters) to deploy this graph project onto your own cluster. Owned hosting is retired: a project we operate must run on your own infrastructure. Register a pool via the Resource Pools UI first, then pass its id here."
    }
  },
  "required": [
    "name",
    "schema",
    "cluster_id"
  ]
}

Update a graph project's schema (saves to database, does NOT deploy). ⚠️ Follow ALL rules from create_graph_project: • Must have "nodes" key with at least one entity • Each entity needs "description" and "schema" with field definitions • Each field is {"type": "...", "required": true/false} — required defaults to false • Relationships need "from", "to", and "cardinality" • Field types: string, integer, float, boolean, date, json • Relationship types should be UPPER_SNAKE_CASE • Entity names should be PascalCase WORKFLOW: 1. Use get_graph_schema to see current schema 2. Modify following all rules 3. Call update_graph_schema (saves only) 4. Call deploy_graph_staging to apply changes 5. Monitor with get_job_status DRY RUN: pass dry_run=true to preview what a deploy WOULD change (renames, deletions) without saving. NOTE: This only saves the schema. You MUST call deploy_graph_staging afterwards to deploy.

{
  "type": "object",
  "properties": {
    "project_id": {
      "type": "string",
      "description": "Project ID (UUID)"
    },
    "schema": {
      "type": "object",
      "description": "New graph schema with 'nodes' and optionally 'relationships' keys."
    },
    "dry_run": {
      "type": "boolean",
      "description": "Preview the planned migration (renames/deletions) without saving or deploying. Nothing is applied."
    }
  },
  "required": [
    "project_id",
    "schema"
  ]
}

Deploy a graph project to the staging environment. This triggers: (1) Schema validation, (2) Neo4j entity code generation, (3) Docker image build, (4) GitHub commit, (5) Kubernetes deployment with Neo4j instance. The operation is ASYNCHRONOUS — returns immediately with a job_id. Use get_job_status to monitor progress. Deployment typically takes 2-5 minutes. Use get_graph_project_info to verify deployment succeeded. A deploy that drops data is refused until you pass confirm_destructive=true after reviewing the plan. One operation runs on a project at a time: while another runs, the call is refused and the refusal names the running job; wait for it with get_job_status, then call again. While RationalBloks is being updated, the call is refused with 'RationalBloks is being updated': call it again in a few minutes.

{
  "type": "object",
  "properties": {
    "project_id": {
      "type": "string",
      "description": "Project ID (UUID)"
    },
    "confirm_destructive": {
      "type": "boolean",
      "description": "Set true only after reviewing the plan: a deploy that drops tables, columns, entities, relationships or fields is refused without it"
    }
  },
  "required": [
    "project_id"
  ]
}

Promote graph staging to production. Creates a separate production Neo4j instance with its own credentials and database. Requires paid plan. A deploy that drops data is refused until you pass confirm_destructive=true after reviewing the plan. One operation runs on a project at a time: while another runs, the call is refused and the refusal names the running job; wait for it with get_job_status, then call again. While RationalBloks is being updated, the call is refused with 'RationalBloks is being updated': call it again in a few minutes.

{
  "type": "object",
  "properties": {
    "project_id": {
      "type": "string",
      "description": "Project ID (UUID)"
    },
    "confirm_destructive": {
      "type": "boolean",
      "description": "Set true only after reviewing the plan: a deploy that drops tables, columns, entities, relationships or fields is refused without it"
    }
  },
  "required": [
    "project_id"
  ]
}

Delete a graph project (removes GitHub repo, K8s deployments, Neo4j database, and credentials). It runs as a job: poll the returned job_id with get_job_status until it is completed. One operation runs on a project at a time: while another runs, the call is refused and the refusal names the running job; wait for it with get_job_status, then call again. While RationalBloks is being updated, the call is refused with 'RationalBloks is being updated': call it again in a few minutes.

{
  "type": "object",
  "properties": {
    "project_id": {
      "type": "string",
      "description": "Project ID (UUID)"
    }
  },
  "required": [
    "project_id"
  ]
}

Rollback a graph project to a previous version. ⚠️ WARNING: This reverts schema AND code to the specified commit. Neo4j data is NOT rolled back. Use get_graph_version_history to find the commit SHA of the version you want to rollback to. After rollback, the graph API will be redeployed with the old schema. One operation runs on a project at a time: while another runs, the call is refused and the refusal names the running job; wait for it with get_job_status, then call again. While RationalBloks is being updated, the call is refused with 'RationalBloks is being updated': call it again in a few minutes.

{
  "type": "object",
  "properties": {
    "project_id": {
      "type": "string",
      "description": "Project ID (UUID)"
    },
    "version": {
      "type": "string",
      "description": "Commit SHA to rollback to"
    },
    "environment": {
      "type": "string",
      "description": "Environment: staging or production (default: staging)"
    }
  },
  "required": [
    "project_id",
    "version"
  ]
}

Create a single node in a deployed graph project. REQUIRES: Project must be deployed (use deploy_graph_staging first). The entity_type must match an entity key from the project schema. Use get_graph_data_schema to see available entity types and their fields. Example: entity_type: "person" entity_id: "alan-turing-001" data: {"name": "Alan Turing", "birth_year": 1912, "field": "Computer Science"} The entity_id is your unique identifier — use meaningful IDs for knowledge graphs.

{
  "type": "object",
  "properties": {
    "project_id": {
      "type": "string",
      "description": "Project ID (UUID)"
    },
    "entity_type": {
      "type": "string",
      "description": "Entity key (e.g., 'person', 'concept')"
    },
    "entity_id": {
      "type": "string",
      "description": "Unique identifier for the node"
    },
    "data": {
      "type": "object",
      "description": "Node properties matching the entity schema"
    },
    "environment": {
      "type": "string",
      "description": "Environment: staging or production (default: staging)"
    }
  },
  "required": [
    "project_id",
    "entity_type",
    "entity_id",
    "data"
  ]
}

Get a specific node by its entity_id from a deployed graph project. Returns all node properties including created_at and updated_at timestamps.

{
  "type": "object",
  "properties": {
    "project_id": {
      "type": "string",
      "description": "Project ID (UUID)"
    },
    "entity_type": {
      "type": "string",
      "description": "Entity key (e.g., 'person', 'concept')"
    },
    "entity_id": {
      "type": "string",
      "description": "The node's entity_id"
    },
    "environment": {
      "type": "string",
      "description": "Environment: staging or production (default: staging)"
    }
  },
  "required": [
    "project_id",
    "entity_type",
    "entity_id"
  ]
}

List nodes of a specific entity type from a deployed graph project. Supports pagination with limit/offset. Returns nodes ordered by creation date (newest first).

{
  "type": "object",
  "properties": {
    "project_id": {
      "type": "string",
      "description": "Project ID (UUID)"
    },
    "entity_type": {
      "type": "string",
      "description": "Entity key (e.g., 'person', 'concept')"
    },
    "limit": {
      "type": "integer",
      "description": "Max results (default: 100, max: 1000)"
    },
    "offset": {
      "type": "integer",
      "description": "Pagination offset (default: 0)"
    },
    "environment": {
      "type": "string",
      "description": "Environment: staging or production (default: staging)"
    }
  },
  "required": [
    "project_id",
    "entity_type"
  ]
}

Update properties of an existing node in a deployed graph project. Only send the fields you want to change — unspecified fields remain unchanged.

{
  "type": "object",
  "properties": {
    "project_id": {
      "type": "string",
      "description": "Project ID (UUID)"
    },
    "entity_type": {
      "type": "string",
      "description": "Entity key (e.g., 'person', 'concept')"
    },
    "entity_id": {
      "type": "string",
      "description": "The node's entity_id"
    },
    "data": {
      "type": "object",
      "description": "Properties to update (partial update)"
    },
    "environment": {
      "type": "string",
      "description": "Environment: staging or production (default: staging)"
    }
  },
  "required": [
    "project_id",
    "entity_type",
    "entity_id",
    "data"
  ]
}

Delete a node and all its relationships from a deployed graph project. ⚠️ This also removes all relationships connected to this node (DETACH DELETE).

{
  "type": "object",
  "properties": {
    "project_id": {
      "type": "string",
      "description": "Project ID (UUID)"
    },
    "entity_type": {
      "type": "string",
      "description": "Entity key (e.g., 'person', 'concept')"
    },
    "entity_id": {
      "type": "string",
      "description": "The node's entity_id"
    },
    "environment": {
      "type": "string",
      "description": "Environment: staging or production (default: staging)"
    }
  },
  "required": [
    "project_id",
    "entity_type",
    "entity_id"
  ]
}

Create a relationship between two nodes in a deployed graph project. The rel_type must match a relationship key from the project schema. Use get_graph_data_schema to see available relationship types. Example: rel_type: "authored" from_id: "alan-turing-001" to_id: "on-computable-numbers-001" data: {"year": 1936} The from_id and to_id must be entity_ids of existing nodes.

{
  "type": "object",
  "properties": {
    "project_id": {
      "type": "string",
      "description": "Project ID (UUID)"
    },
    "rel_type": {
      "type": "string",
      "description": "Relationship key (e.g., 'authored', 'related_to')"
    },
    "from_id": {
      "type": "string",
      "description": "Source node entity_id"
    },
    "to_id": {
      "type": "string",
      "description": "Target node entity_id"
    },
    "data": {
      "type": "object",
      "description": "Relationship properties (optional)"
    },
    "environment": {
      "type": "string",
      "description": "Environment: staging or production (default: staging)"
    }
  },
  "required": [
    "project_id",
    "rel_type",
    "from_id",
    "to_id"
  ]
}

Get all relationships connected to a specific node. Supports direction filtering (incoming, outgoing, both) and relationship type filtering.

{
  "type": "object",
  "properties": {
    "project_id": {
      "type": "string",
      "description": "Project ID (UUID)"
    },
    "entity_type": {
      "type": "string",
      "description": "Entity key of the node"
    },
    "entity_id": {
      "type": "string",
      "description": "The node's entity_id"
    },
    "direction": {
      "type": "string",
      "description": "Filter: incoming, outgoing, or both (default: both)"
    },
    "rel_type_filter": {
      "type": "string",
      "description": "Filter by relationship type (UPPER_SNAKE_CASE)"
    },
    "environment": {
      "type": "string",
      "description": "Environment: staging or production (default: staging)"
    }
  },
  "required": [
    "project_id",
    "entity_type",
    "entity_id"
  ]
}

Delete a specific relationship by its internal ID. Use get_node_relationships to find relationship IDs.

{
  "type": "object",
  "properties": {
    "project_id": {
      "type": "string",
      "description": "Project ID (UUID)"
    },
    "rel_type": {
      "type": "string",
      "description": "Relationship key"
    },
    "rel_id": {
      "type": "integer",
      "description": "Internal relationship ID (from get_node_relationships)"
    },
    "environment": {
      "type": "string",
      "description": "Environment: staging or production (default: staging)"
    }
  },
  "required": [
    "project_id",
    "rel_type",
    "rel_id"
  ]
}

Create multiple nodes at once (up to 500 per call). Uses Neo4j UNWIND for high performance. Essential for knowledge graph population — create hundreds of entities from a single book chapter or article. Each node needs: entity_id (unique string) and data (properties dict). Example: entity_type: "concept" nodes: [ {"entity_id": "quantum-mechanics-001", "data": {"name": "Quantum Mechanics", "field": "Physics"}}, {"entity_id": "wave-function-001", "data": {"name": "Wave Function", "field": "Physics"}}, {"entity_id": "superposition-001", "data": {"name": "Superposition", "field": "Physics"}} ]

{
  "type": "object",
  "properties": {
    "project_id": {
      "type": "string",
      "description": "Project ID (UUID)"
    },
    "entity_type": {
      "type": "string",
      "description": "Entity key for all nodes"
    },
    "nodes": {
      "type": "array",
      "description": "List of nodes. Each: {entity_id: string, data: {properties}}",
      "items": {
        "type": "object",
        "properties": {
          "entity_id": {
            "type": "string"
          },
          "data": {
            "type": "object"
          }
        },
        "required": [
          "entity_id",
          "data"
        ]
      }
    },
    "environment": {
      "type": "string",
      "description": "Environment: staging or production (default: staging)"
    }
  },
  "required": [
    "project_id",
    "entity_type",
    "nodes"
  ]
}

Create multiple relationships at once (up to 500 per call). Uses Neo4j UNWIND for high performance. Essential for connecting knowledge — link hundreds of concepts, people, and events in one operation. Each relationship needs: from_id, to_id, and optional data (properties). Example: rel_type: "related_to" relationships: [ {"from_id": "quantum-mechanics-001", "to_id": "wave-function-001", "data": {"strength": "strong"}}, {"from_id": "quantum-mechanics-001", "to_id": "superposition-001", "data": {"strength": "strong"}} ]

{
  "type": "object",
  "properties": {
    "project_id": {
      "type": "string",
      "description": "Project ID (UUID)"
    },
    "rel_type": {
      "type": "string",
      "description": "Relationship key for all relationships"
    },
    "relationships": {
      "type": "array",
      "description": "List of relationships. Each: {from_id, to_id, data?}",
      "items": {
        "type": "object",
        "properties": {
          "from_id": {
            "type": "string"
          },
          "to_id": {
            "type": "string"
          },
          "data": {
            "type": "object"
          }
        },
        "required": [
          "from_id",
          "to_id"
        ]
      }
    },
    "environment": {
      "type": "string",
      "description": "Environment: staging or production (default: staging)"
    }
  },
  "required": [
    "project_id",
    "rel_type",
    "relationships"
  ]
}

Search for nodes by property values in a deployed graph project. Supports exact match and contains search (prefix value with ~ for contains). Examples: Exact: filters: {"name": "Alan Turing"} Contains: filters: {"name": "~turing"} (case-insensitive) Combined: entity_type: "person", filters: {"field": "~physics"} Without entity_type, searches ALL node types.

{
  "type": "object",
  "properties": {
    "project_id": {
      "type": "string",
      "description": "Project ID (UUID)"
    },
    "entity_type": {
      "type": "string",
      "description": "Entity key to filter by (optional — omit to search all types)"
    },
    "filters": {
      "type": "object",
      "description": "Property filters. Prefix value with ~ for contains search."
    },
    "limit": {
      "type": "integer",
      "description": "Max results (default: 100, max: 1000)"
    },
    "offset": {
      "type": "integer",
      "description": "Pagination offset (default: 0)"
    },
    "environment": {
      "type": "string",
      "description": "Environment: staging or production (default: staging)"
    }
  },
  "required": [
    "project_id",
    "filters"
  ]
}

Search across ALL string properties of ALL nodes in a deployed graph using free-text queries. Unlike search_graph_nodes (which filters by specific property), this searches every text field at once. Perfect for finding knowledge when you don't know which property contains the answer. Example: query "quantum" searches name, description, summary, notes, and all other string fields. Returns nodes with _match_fields showing which properties matched. Optionally filter by entity_type to narrow results.

{
  "type": "object",
  "properties": {
    "project_id": {
      "type": "string",
      "description": "Project ID (UUID)"
    },
    "query": {
      "type": "string",
      "description": "Search text (case-insensitive, min 2 chars)"
    },
    "entity_type": {
      "type": "string",
      "description": "Entity key to filter by (optional — omit to search all types)"
    },
    "limit": {
      "type": "integer",
      "description": "Max results (default: 50, max: 500)"
    },
    "offset": {
      "type": "integer",
      "description": "Pagination offset (default: 0)"
    },
    "environment": {
      "type": "string",
      "description": "Environment: staging or production (default: staging)"
    }
  },
  "required": [
    "project_id",
    "query"
  ]
}

Walk the graph from a starting node, discovering connected knowledge. Returns all nodes reachable within max_depth hops, with their distance from the start. Essential for exploring knowledge graphs — find related concepts, trace connections, discover clusters. Example: Start from "Alan Turing", traverse outgoing relationships up to 3 hops deep: start_entity_type: "person" start_entity_id: "alan-turing-001" max_depth: 3 direction: "outgoing" Supports filtering by relationship types and direction.

{
  "type": "object",
  "properties": {
    "project_id": {
      "type": "string",
      "description": "Project ID (UUID)"
    },
    "start_entity_type": {
      "type": "string",
      "description": "Entity key of the starting node"
    },
    "start_entity_id": {
      "type": "string",
      "description": "Entity ID of the starting node"
    },
    "max_depth": {
      "type": "integer",
      "description": "Maximum traversal depth (default: 3, max: 10)"
    },
    "relationship_types": {
      "type": "array",
      "description": "Filter by relationship types (UPPER_SNAKE_CASE). Omit for all types.",
      "items": {
        "type": "string"
      }
    },
    "direction": {
      "type": "string",
      "description": "Direction: outgoing, incoming, or both (default: both)"
    },
    "limit": {
      "type": "integer",
      "description": "Max results (default: 100, max: 1000)"
    },
    "environment": {
      "type": "string",
      "description": "Environment: staging or production (default: staging)"
    }
  },
  "required": [
    "project_id",
    "start_entity_type",
    "start_entity_id"
  ]
}

Get statistics about a deployed graph: total node count, total relationship count, counts per entity type, counts per relationship type. Essential for understanding the current state of a knowledge graph before adding more data.

{
  "type": "object",
  "properties": {
    "project_id": {
      "type": "string",
      "description": "Project ID (UUID)"
    },
    "environment": {
      "type": "string",
      "description": "Environment: staging or production (default: staging)"
    }
  },
  "required": [
    "project_id"
  ]
}

Get the runtime schema of a DEPLOYED graph project — shows the actual entity types and relationship types available for data operations. Returns: Available entity keys (for create_graph_node, list_graph_nodes, etc.) and relationship keys (for create_graph_relationship, etc.). ⭐ USE THIS FIRST before creating nodes/relationships to know what entity_type and rel_type values are valid.

{
  "type": "object",
  "properties": {
    "project_id": {
      "type": "string",
      "description": "Project ID (UUID)"
    },
    "environment": {
      "type": "string",
      "description": "Environment: staging or production (default: staging)"
    }
  },
  "required": [
    "project_id"
  ]
}