Geond Agent Protocol

Get symbol context

get_symbol_context

Retrieve definitions and changesets for code symbols to understand their context before making edits.

Instructions

Purpose: Find known code graph entities that match a symbol name. When to use: call before modifying a function, class, method, or variable so the agent can see definitions and related changesets. Inputs: symbol is the name to match; limit caps returned entities. Side effects: none beyond database reads. Output: matching entities with file locations, workspace data, related changesets, and evidence refs. Failure modes: returns an empty list when the code graph has not indexed the symbol.

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": {
      "symbol": "<symbol>"
    },
    "name": "get_symbol_context"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No	Maximum number of matching code entities to return.
`symbol`	Yes	Function, class, method, or other code symbol name to look up.

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jun 3, 2026

TDQS

A4.4/5.0

Behavior5/5

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

With no annotations provided, the description fully covers behavioral traits: side effects ('none beyond database reads'), output details (file locations, workspace data, related changesets, evidence refs), and failure modes ('returns an empty list when the code graph has not indexed the symbol'). This is comprehensive.

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?

The description is well-structured with labeled sections (Purpose, When to use, Inputs, Side effects, Output, Failure modes). It is concise but not overly terse; every section adds value. Could be slightly more compact without losing clarity.

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

Completeness5/5

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

Given the presence of an output schema and the tool's straightforward nature (lookup by symbol), the description covers all essential aspects: purpose, usage context, inputs, side effects, output, and failure modes. It is fully complete for an agent to understand invocation.

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%, so baseline is 3. The description's explanation of parameters ('symbol is the name to match; limit caps returned entities') adds minimal meaning beyond the schema descriptions, which already define the parameters adequately.

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

Purpose5/5

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

The description clearly states the verb 'find' and the resource 'code graph entities', and specifies matching by symbol name. It distinguishes itself from sibling tools like explain_change and get_changeset_detail, which focus on changes or workspace data, by focusing on code graph entity lookup.

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

Usage Guidelines4/5

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

The description explicitly says when to use: 'call before modifying a function, class, method, or variable so the agent can see definitions and related changesets'. It provides a clear context but does not mention when not to use or alternative tools, which would make it more complete.

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