Skip to main content
Glama

read_only_cypher

Read-onlyIdempotent

Run read-only Cypher queries against the operations graph to inspect data safely; writes, LOAD CSV, and dbms/apoc procedures are blocked.

Instructions

Run your own read-only Cypher. Refuses writes, LOAD CSV and dbms/apoc procedures; 5 s timeout; at most 200 rows.

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

Input Schema

NameRequiredDescriptionDefault
queryYes
paramsNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the description is not needed for the safety profile. It nonetheless adds real context beyond them: the enforced rejection of writes, LOAD CSV and dbms/apoc, a 5 s timeout, and a 200-row cap. What it omits is how a refused query surfaces (error type/message) and whether multi-statement input is allowed.

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?

One front-loaded sentence followed by a semicolon-separated constraint list; every clause (refusals, timeout, row cap) carries operationally relevant information. There is no filler and nothing is buried.

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

Completeness3/5

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

The output schema means return values need not be explained, and the enforcement limits are well covered. However, for a free-form query execution tool the gaps that matter are the unaddressed `params` argument and the unspecified error behavior when a query is refused, which leaves the definition adequate but not complete.

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% – neither `query` nor `params` carries a description – and the description never mentions the `params` argument at all. An agent must infer from convention that `params` supplies Cypher query parameters; the definition does not confirm or illustrate it, nor does it state that only a single statement is expected.

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 your own ... Cypher") plus a scope qualifier (read-only), which immediately frames this as the raw-query escape hatch versus the domain-specific siblings like impact_analysis or reconciliation_report. It stops short of explicitly naming any sibling or contrasting with them, so differentiation is inferable rather than stated.

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 word "your own" implies this is for queries the curated tools do not cover, but there is no explicit "use this when X, prefer Y otherwise" guidance and no prerequisites. The constraints given (refuses writes, LOAD CSV, dbms/apoc) describe what is rejected rather than when to reach for the tool.

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