Skip to main content
Glama
MCK564

token-context-mcp

by MCK564
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Symbol context

get_symbol_context

Retrieve a bounded, source-hashed code packet for an indexed symbol, including observed edges and freshness or ambiguity warnings. Read oversized bodies in windows via body_offset_line.

Instructions

Bounded source packet for indexed symbol and observed edges. Check freshness and ambiguity warnings. A body larger than max_tokens is read in windows with body_offset_line.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
depthNo
profileNo
repo_idYes
symbol_idYes
max_tokensNo
include_bodyNo
body_offset_lineNo
include_omitted_idsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.3.3
    • addedInput schema / properties / body_offset_line
      Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Body Offset Line"
+}
  2. First observedv0.1.0

TDQS

C2.9/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 behavioral burden. It usefully discloses that the result is bounded and that large bodies are read in windows via max_tokens and body_offset_line, but it omits permissions, error behavior, and freshness/ambiguity warning semantics.

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 short and front-loads the core purpose, then adds two relevant behavioral notes. It avoids repetition, though the wording is terse enough that some important details feel compressed rather than clarified.

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?

For an 8-parameter tool with no annotations, no output schema, and 0% schema description coverage, the description is materially incomplete. It covers the surface purpose and windowing behavior but leaves most parameters, return structure, and alternative-tool selection unexplained.

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% and there are 8 parameters, so the description must compensate. It explains only max_tokens and body_offset_line indirectly; depth, profile, include_body, include_omitted_ids, repo_id, and symbol_id remain undocumented beyond their titles.

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?

The description identifies a specific resource: a bounded source packet for an indexed symbol plus observed edges. It communicates what the tool returns, but it does not distinguish the tool from siblings such as inspect_symbol or get_file_skeleton, so an agent must infer the boundary.

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

Usage Guidelines2/5

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

It gives output-related advice ('Check freshness and ambiguity warnings') but does not state when to choose this tool over alternatives like inspect_symbol or find_symbols. No prerequisites, exclusions, or selection criteria are provided.

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