Skip to main content
Glama

Gate Graph Query

gate_graph_query

Query symbol dependency graphs to find dependencies, dependents, file symbols, stats, and graphify hubs; searches auto-fallback to graphify maps when no symbol hits.

Instructions

Symbol graph + graphify map. graphify_map/search/hubs for communities. search auto-fallback. See gate_help recommended_stack.

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": "gate_graph_query"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesSymbol name, file name, or search term to query
rebuildNoForce rebuild the graph (invalidates cache)
queryTypeNoSymbol: search | depends_on | dependents | file_symbols | stats | symbol_map | export_html. Graphify map (nested graphify-out/): graphify_hubs | graphify_search | graphify_map. search auto-fallback to graphify when 0 symbol hits.search
projectRootNoProject root directory (defaults to cwd)
tokenBudgetNoToken budget for queryType=symbol_map (default 1200)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.12

TDQS

C2.7/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 disclosure burden. It notes the auto-fallback behavior of search, which is genuinely useful, but says nothing about the cost of rebuilding the graph, what the cache invalidates, whether the operation is read-only, or what shape results take across the ten query types.

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

Conciseness3/5

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

It is short and front-loads the resource, but the writing is telegraphic fragments rather than structured sentences, and the ordering (graphify hint before any statement of what the tool does) makes the first read ambiguous. Nothing is padded, but clarity is sacrificed for brevity.

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?

This is a ten-mode, five-parameter graph tool with no annotations and no output schema, and the description never explains what any mode returns or what "communities" or "hubs" mean in practice. Given that complexity, far more context is required than four fragments.

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% and the queryType enum documentation already explains every mode including the fallback, so the schema does the heavy lifting. The description repeats the graphify modes without adding syntax, defaults, or trade-offs beyond what the schema states.

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

Purpose3/5

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

The description names the resources ("Symbol graph + graphify map") but never supplies a verb or a plain statement of what the tool returns, and the two coupled capabilities (symbol graph vs. graphify map) are only distinguishable by cross-referencing the queryType enum. An agent can guess it queries some code graph, but the purpose is inferred 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?

"graphify_map/search/hubs for communities" and "search auto-fallback" imply when to pick the graphify query types, and "See gate_help recommended_stack" points at external routing help. There is no when-not guidance and no explanation of when the symbol-graph types are preferable, so usage is only implied.

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