Skip to main content
Glama
Sign In
Gantry

Gantry

by fourn9
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

state

Read-only

Retrieve a versioned snapshot of robotics development context—artifacts, changes, evidence, reviews, and execution context—scoped by basis, intent, or as-of sequence.

Instructions

state

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": {
      "arguments": "<arguments>"
    },
    "name": "state"
  }
}

Input Schema

NameRequiredDescriptionDefault
argumentsYes
idempotency_keyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.4.0

TDQS

D1/5.0
Behavior1/5

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

Annotations declare readOnlyHint=true and destructiveHint=false, which is the only behavioral signal available. The description adds nothing about what state is returned, what basis/intent mean, whether a sequence snapshot is required, or what happens on an invalid as_of_seq, so it earns no credit beyond the structured fields.

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

Conciseness1/5

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

A one-word description is not concise but under-specified; there is no structure, no front-loading, and no sentence that could earn its place because no informative sentence exists.

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

Completeness1/5

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

With two parameters at 0% description coverage, two nested free-form objects, no output schema, and heavy sibling overlap, this definition is far too thin to support correct invocation. Nothing tells an agent what a valid 'arguments' payload looks like.

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

Parameters1/5

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

Schema description coverage is 0% across a required nested 'arguments' object containing opaque 'basis' and 'intent' objects plus 'as_of_seq', and an idempotency_key. The description provides zero clarification of these, so the most ambiguous parameters in the toolset are left completely undefined.

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

Purpose1/5

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

Tautological: description restates name/title.

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

Usage Guidelines1/5

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

There is no when-to-use guidance, no exclusions, and no reference to any of the ~40 sibling tools that plausibly overlap (development_state, get_development_state, context, history). The agent is left to guess entirely.

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

Deploy Server

Other Tools