Skip to main content
Glama
Sign In

JillionDB

by com.jilliondb
OverviewDiscussionsAdmin

Propose a schema change

propose_change

Proposes a schema change for the user to review in JillionDB. Nothing changes until they approve it. Send exactly one of "operations" (preferred: renames are explicit, so no data is lost) or "sql" (the complete desired schema as CREATE TABLE statements; a dropped and re-added column is flagged as a possible rename). Returns the risk of each change and a review link to give the user.

Each operation is an object with "op" and the fields below. Names are table and column names as they appear in get_schema.

  • create_table: table, columns [{name, type, nullable?, default?, unique?, primary_key?, comment?, references?}], primary_key? [names], comment?

  • drop_table: table

  • rename_table: table, to

  • add_column: table, column {name, type, nullable?, default?, unique?, comment?, references?}

  • drop_column: table, column

  • rename_column: table, column, to

  • alter_column: table, column, type?, nullable?, default?, unique?, comment?

  • add_index: table, columns [names], unique?, name?

  • drop_index: table, name or columns

  • add_foreign_key: table, columns [names], references {table, columns? (defaults to its primary key), on_delete?}

  • drop_foreign_key: table, columns or name

  • set_primary_key: table, columns

  • add_check: table, expression, name?

  • drop_check: table, name or expression

  • set_comment: table, column?, comment Types: uuid, text, varchar(n), char(n), smallint, integer, bigint, serial, bigserial, decimal(p,s), float, double, boolean, date, time, timestamp, timestamptz, json, binary, enum('a','b'). Defaults: a value (string, number, true/false), "now", "uuid", "autoincrement", {"value": ...} for literal text that looks like a keyword, or {"sql": "..."} for a raw expression. references: {table, column?, on_delete?: cascade | restrict | set null | set default | no action}.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "project_id": "<project_id>",
      "summary": "<summary>"
    },
    "name": "propose_change"
  }
}

Input Schema

NameRequiredDescriptionDefault
sqlNo
summaryYesOne sentence the reviewer reads first: what changes and why.
operationsNo
project_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses that changes are non-destructive until approval, that sql-mode drops/re-adds are flagged as possible renames, and that the return includes per-change risk plus a review link. Missing are permission requirements and failure/invalid-operation 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?

Front-loaded with the key behavioral constraint before the reference material, and the operation list is dense but necessary for an open-ended object parameter. The type/default vocabulary adds length that could arguably be schema enums, but no sentence is filler.

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?

No output schema exists, and the description does cover the return shape (risk per change, review link to hand the user). Given the complexity of the operations grammar, the definition is largely self-sufficient; only edge cases like conflicting proposals or validation errors are absent.

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 only 25%, yet the description compensates extensively: it enumerates every operation variant with its fields, documents the allowed type vocabulary, and specifies the several shapes of 'default' values including escape hatches for keyword-looking text and raw SQL.

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 and resource ('Proposes a schema change') and immediately clarifies the consequential semantics ('Nothing changes until they approve it'), which separates it from get_proposal/list_proposals siblings that only read proposals.

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?

Explicitly tells the agent to send exactly one of 'operations' or 'sql', and declares 'operations' preferred with the reason (renames explicit, no data loss). It stops short of saying when not to propose (e.g. when a proposal already exists), so not a 5.

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

All JillionDB toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources