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 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.

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
Behavior5/5

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

Annotations already mark this as readOnly=false and destructive=false. The description adds valuable behavioral context beyond those annotations: deployment takes 2-5 minutes, the call can be refused transiently, a cluster_id is required because owned hosting is retired, and the result should be monitored via get_job_status. No contradiction with annotations exists.

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?

The description is long but well-structured with a warning header, schema example, field types, cardinality options, hierarchical example, numbered rules, and workflow. It is front-loaded with the purpose. Minor redundancy exists because 'Use get_graph_template_schemas FIRST' appears in both Rule 8 and Workflow step 1, but the length is justified by the complexity of the schema format.

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

Completeness5/5

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

The description is highly complete for a complex creation tool: it documents the required schema shape, field types, relationship cardinalities, naming conventions, required and optional keys, automatic fields, deployment behavior, and monitoring workflow. Even without an output schema, it tells the caller that a job_id is returned for status tracking.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3. The description adds substantial meaning beyond the schema by documenting the exact graph schema structure: nodes, relationships, field types, cardinality, hierarchical inheritance, and validation rules. It does not add much for name or cluster_id, but those are already well documented in the input schema.

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 description opens with 'Create a new Neo4j graph database project from a hierarchical JSON schema', a specific verb, resource, and input format. This clearly distinguishes it from generic create_project and from node/relationship-level graph tools such as create_graph_node and create_graph_relationship.

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

Usage Guidelines4/5

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

The description gives a clear workflow: first use get_graph_template_schemas, then call this tool, then monitor with get_job_status. It also states when to retry during the 'RationalBloks is being updated' refusal. It does not explicitly list when-not-to-use conditions or name alternative creation tools, but the context and workflow are clear enough.

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
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources