Skip to main content
Glama

RationalBloks

by io.github.rationalbloks
OverviewDiscussionsAdmin

Create Graph Project

create_graph_project

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 an entity inside its parent entity (beside "description", "flat_labels" and "schema") to create a type hierarchy; the child inherits the parent's labels: "Animal": {"description": "...", "schema": {...}, "Dog": {"description": "...", "schema": {...}}}

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

WORKFLOW:

  1. get_graph_template_schemas FIRST to see valid examples

  2. create_graph_project with a cluster_id from list_clusters

  3. Poll get_job_status with the returned job_id (2-5 minutes) While RationalBloks is being updated, the call is refused with 'RationalBloks is being updated': call it again in a few minutes.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesProject name
schemaYesGraph schema with 'nodes' and optionally 'relationships' keys. Use get_graph_template_schemas to see valid examples.
cluster_idYesREQUIRED — 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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / properties / description
      Removed value: -{
-  "description": "Optional project description",
-  "type": "string"
-}
  2. Changed2 schema fields changed
    • changedInput schema / properties / cluster_id / description
      Previous value: -"Optional BYOC resource pool ID (from list_clusters) to deploy this project onto your own cluster. Omit to deploy on RationalBloks-hosted infrastructure."New value: +"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."
    • changedInput schema / required
      Previous value: -[
-  "name",
-  "schema"
-]New value: +[
+  "name",
+  "schema",
+  "cluster_id"
+]
  3. Changed1 schema field changed
    • addedInput schema / properties / cluster_id
      Added value: +{
+  "description": "Optional BYOC resource pool ID (from list_clusters) to deploy this project onto your own cluster. Omit to deploy on RationalBloks-hosted infrastructure.",
+  "type": "string"
+}
  4. Added

TDQS

A4.6/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnly=false, destructive=false, and openWorld=false, so the safety profile is covered. The description adds genuinely non-obvious behavior: the operation is asynchronous (returns a job_id that must be polled for 2-5 minutes) and requires BYOC hosting, plus a retry note when the backend is updating. The retry sentence is garbled but still conveys recovery behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Despite its length, the content is front-loaded and organized under clear headers (SCHEMA STRUCTURE, FIELD TYPES, RULES, WORKFLOW), and the format detail is arguably necessary for a free-form nested schema parameter. It loses a point for the malformed trailing sentence about RationalBloks, which reads as a truncated fragment.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a mutation tool with three required parameters and no output schema, the description covers the schema format, deployment prerequisite (register a pool, pass its id), and async follow-up thoroughly. The only gap is that the garbled RationalBloks retry sentence leaves error-handling behavior slightly unclear.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline would be 3, but the description goes well beyond the schema's one-line 'schema' definition by spelling out the full JSON structure, field types, cardinality options, hierarchical nesting, and naming conventions. This is substantial added meaning for the most complex parameter.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The opening sentence states a specific verb and resource: 'Create a new Neo4j graph database project from a hierarchical JSON schema.' The 'graph database project' phrasing distinguishes it from the plain create_project sibling, and the schema-format emphasis makes the intent unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The WORKFLOW block gives explicit ordering and prerequisites: call get_graph_template_schemas first, supply a cluster_id from list_clusters, then poll get_job_status with the returned job_id. This tells the agent exactly when and how to sequence the call relative to siblings.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All RationalBloks toolsInspect
Try in Browser
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources