Skip to main content
Glama
Sign In
code-explorer

code-explorer

by vmikhailov
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

save_project_query

Save reusable Cypher queries with metadata into .codeexplorer/queries/ so you can organize and reuse code-explorer queries later.

Instructions

Save a reusable Cypher query with metadata into .codeexplorer/queries/.

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

Input Schema

NameRequiredDescriptionDefault
nameYesQuery identifier (e.g. 'find_kafka_consumers').
tagsNoOptional comma-separated tags.
cypherYesCypher query text with parameters ($param, etc.).
returnsNoOptional description of returned fields.
parametersNoOptional parameter schema YAML list.
descriptionYesQuery purpose description.
workspacePathNoOptional workspace root path.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.80.5

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It discloses the write target directory, but says nothing about overwrite behavior for a duplicate name, whether the directory is auto-created, permission requirements, or what the tool returns on success — all material for a filesystem-mutating tool with a required 'name' acting as an identifier.

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?

A single tight sentence with the destination front-loaded after the action; nothing is wasted. Its brevity is appropriate to the format, though it leaves nuance to the other dimensions.

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

Completeness2/5

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

With no annotations, no output schema, and a mutation that writes to disk, the description should cover overwrite semantics and at least hint at success behavior. The presence of a required 'name' as identifier plus 100% schema coverage mitigates this somewhat, but key operational facts are absent.

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

Parameters3/5

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

Schema description coverage is 100%, so all seven parameters are already documented in the schema; the description only adds the framing that metadata is saved alongside the Cypher text, which loosely maps to tags/returns/parameters/description. It adds no syntax or validation detail beyond the schema, so baseline 3 applies.

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 ('Save a reusable Cypher query') plus the persistence location ('.codeexplorer/queries/'), so the agent knows exactly what the call does. It does not name or distinguish itself from siblings like list_project_queries or execute_project_query, which keeps it short of a 5.

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?

Usage is only implied via the word 'reusable' — an agent can infer the saved query is meant to be retrieved or executed later, but there is no explicit when-to-use statement, no mention of prerequisites, and no guidance on when to save versus just executing ad hoc.

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