Skip to main content
Glama
Sign In

RationalBloks

by io.github.rationalbloks
OverviewDiscussionsAdmin

Create Project

create_project

Create a new RationalBloks project (a PostgreSQL REST API) from a JSON schema, on one of your resource pools.

⚠️ CRITICAL RULES - READ BEFORE CREATING SCHEMA:

  1. FLAT FORMAT (REQUIRED): ✅ CORRECT: {"orders": {"total": {"type": "decimal", "precision": 10, "scale": 2}}} ❌ WRONG: {"orders": {"fields": {...}}} — never nest under 'fields'

  2. EVERY field has a "type": string (MUST have max_length), text, integer, decimal (precision, scale), boolean, uuid, date, datetime (NOT "timestamp"), json, and the PostgreSQL arrays uuid_array, integer_array, text_array, float_array (GIN-indexed: @> contains, <@ contained_by, && overlaps)

  3. AUTOMATIC FIELDS (DON'T define): id, created_at, updated_at, row_version

  4. USERS: NEVER create users/customers/employees tables with email or password. Link to the built-in app_users table: {"user_id": {"type": "uuid", "foreign_key": "app_users.id"}}. A table with such a field is owner-scoped: each user sees their own rows.

  5. FIELD OPTIONS: required, unique, default, enum, foreign_key ("table.id"), on_delete (cascade, set_null, restrict, no_action), nullable, index, description, write_only, computed. Advanced features (policy, computed columns, constraints, audit): get_schema_reference.

BACKEND ENGINE (backend_type): "python" (FastAPI, default) or "rust" (Axum: faster cold starts, lower memory).

WORKFLOW:

  1. get_template_schemas FIRST to see valid examples

  2. create_project with a cluster_id from list_clusters

  3. Poll get_job_status with the returned job_id (2-5 minutes)

  4. get_project_info gives the live URL While RationalBloks is being updated, the call is refused with 'RationalBloks is being updated': call it again in a few minutes.

Input Schema

NameRequiredDescriptionDefault
nameYesProject name
schemaYesJSON schema in FLAT format (table_name → field_name → properties). Every field MUST have a 'type' property. Use get_template_schemas to see valid examples.
cluster_idYesREQUIRED — 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.
backend_typeNoBackend engine: 'python' (FastAPI, default) or 'rust' (Axum, faster). Default: python

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 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. Changed1 schema field changed
    • addedInput schema / properties / backend_type
      Added value: +{
+  "description": "Backend engine: 'python' (FastAPI, default) or 'rust' (Axum, faster). Default: python",
+  "enum": [
+    "python",
+    "rust"
+  ],
+  "type": "string"
+}
  5. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Goes well beyond the annotations (which only cover safety hints) by disclosing the async job model (returns job_id, 2-5 minute completion), the update-refusal behavior and retry guidance, and schema-validity constraints that cause rejection. It does not mention permissions, quotas, or what partial-failure/rollback looks like, keeping it short of a 5.

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?

Front-loaded with purpose, then critical schema rules, then backend choice, then workflow. Long and emoji-heavy, but nearly every line prevents a concrete creation failure; a little redundant with the schema's own field descriptions.

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?

For a complex, multi-param, no-output-schema creation tool this covers the essentials: what it makes, what it needs, the format rules, the async lifecycle and how to obtain the resulting URL. Nothing an agent needs to invoke it correctly is missing.

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 description coverage is 100%, so baseline is 3. The description still adds semantic value: cluster_id is mandatory because owned hosting is retired and the pool must be pre-registered, backend_type contrasts FastAPI vs Axum trade-offs, and the flat-format rules for the schema parameter clarify its expected shape.

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?

States a specific verb+resource: 'Create a new RationalBloks project (a PostgreSQL REST API) from a JSON schema, on one of your resource pools.' This distinguishes it cleanly from create_graph_project, deploy_*, and get_template_schemas among the many siblings.

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?

An explicit WORKFLOW section gives ordered when-to-use steps: call get_template_schemas first, then create_project with a cluster_id from list_clusters, then poll get_job_status, then get_project_info. It also states the retry condition for the 'RationalBloks is being updated' refusal.

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