Look up a single node by ID in the repository's knowledge graph, linking code files to aSPARK delivery artifacts for traceability and impact analysis.
Look up a single node by its id (e.g. 'file:src/foo.py').
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | ||
| repo | No | . |
Changes observed during successful MCP inspections.
v0.7.1v0.4.0v0.3.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, description carries full burden. Only states 'look up a single node' without disclosing return format, side effects, authorization, or any constraints.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Single sentence with no wasted words. Front-loaded with core purpose.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
No output schema and no annotations; description fails to explain return value structure or error handling. Too minimal for a tool likely returning a complex node object.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage 0%; description only mentions 'id' with an example but ignores the 'repo' parameter entirely. Does not explain parameter meanings beyond a format hint for id.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Description clearly states the verb 'look up' and resource 'single node by its id', with a concrete example of the id format. Differentiates from sibling tools like find_nodes by specifying singleton lookup.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when to use this tool versus alternatives like find_nodes or get_neighbors. Does not mention prerequisites or contexts.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.