Skip to main content
Glama
Sign In
code-explorer

code-explorer

by vmikhailov
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

list_project_queries

Retrieve saved project-specific Cypher queries from the .codeexplorer/queries directory to reuse existing analysis instead of rewriting graph queries for each workspace.

Instructions

List saved project-specific Cypher queries in .codeexplorer/queries/.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_project_queries"
  }
}

Input Schema

NameRequiredDescriptionDefault
workspacePathNoOptional workspace root path.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.80.5

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It reveals the storage path (.codeexplorer/queries/) and the read-only nature implied by "List," but says nothing about behavior when the directory is absent, whether an empty list is returned, or what the results look like.

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 sentence, front-loaded with the verb and resource, with no filler. Every element (saved, project-specific, Cypher, path) adds discriminating information.

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?

For a simple one-parameter read tool this is close to adequate, but with no output schema the description should describe what a listing entry contains (query names? file paths? query text?), and it omits any workspace-initialization precondition.

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 coverage is 100% and the single optional workspacePath parameter is already documented in the schema, so the baseline is 3. The description's "project-specific" wording hints that results are scoped to a workspace but adds no format or default guidance beyond that.

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 ("List") and a specific resource ("saved project-specific Cypher queries"), plus the storage location. An agent can tell it apart from execute_project_query or save_project_query by the word "saved" and the listing verb, though no sibling is named 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?

Usage is only implied: "saved" queries suggests a discovery step before execute_project_query, but the description never says when to call this versus executing a query directly, nor any prerequisites such as an initialized workspace.

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