Skip to main content
Glama

query

Run read-only Cypher against the Strata archaeological graph to inspect stratigraphic units, finds, periods, and record contradictions; results return columns, limited rows, and truncation status.

Instructions

Run a read-only Cypher query against the store (it is always rolled back). Returns columns, rows (at most limit) and whether rows were cut.

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": {
      "cypher": "<cypher>"
    },
    "name": "query"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
cypherYes
paramsNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.6/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 disclose the critical behavior: execution is read-only and always rolled back, so no state persists. It also describes the response shape (columns, rows, whether rows were cut), which reassures the agent about truncation. It does not say what happens on invalid Cypher or syntax errors.

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

Conciseness5/5

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

Two short sentences, front-loaded with the action and its safety property, followed by return behavior. No filler or repetition.

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 three-parameter tool with an output schema, the description covers the essential safety contract and truncation semantics. The remaining gap is how `params` are bound into the query, which matters for correct invocation but is not addressed.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate for all three parameters. It only adds meaning for `limit` ('at most limit' rows) and implicitly clarifies `cypher`; the `params` binding parameter (nullable object) is never explained, leaving the least obvious argument undocumented.

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

Purpose4/5

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

States a specific verb and resource: 'Run a read-only Cypher query against the store', plus a key scope constraint (always rolled back). It is clearly distinct from a read-only introspection tool like describe or overview, though it does not name any sibling explicitly.

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

Usage Guidelines3/5

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

The 'read-only ... always rolled back' note implies safe exploratory use, and the limit/cut-rows mention hints at large result sets, but there is no explicit when-to-use-this-instead-of guidance (e.g., versus describe or overview for schema questions). Usage is implied rather than stated.

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