Skip to main content
Glama

Build Call Path

build_call_path
Idempotent

Builds shortest direct-callee paths inline from complete analyze_function Evidence records using exact canonical addresses, with every node and edge citing source Evidence.

Instructions

Build every shortest direct-callee path inline from complete analyze_function Evidence records using exact canonical addresses. Missing dossiers and provider mixing remain unknown; every node and edge cites source Evidence.

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": {
      "functions": "<functions>",
      "start": "<start>",
      "goal": "<goal>"
    },
    "name": "build_call_path"
  }
}

Input Schema

NameRequiredDescriptionDefault
goalYes
startYes
functionsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, and destructiveHint=false. The description adds useful behavioral context: missing dossiers and provider mixing remain unknown, and every node and edge cites source Evidence. It does not clarify whether the built path is persisted, returned inline, or how the non-read-only behavior manifests.

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 definition is compact and front-loaded, with the core action stated first and the limitation/provenance note second. The wording is dense but every sentence contributes 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 tool with three required parameters, a complex Evidence array, and no output schema, the description gives the data source and hints at output provenance. It still leaves important invocation details and return-shape specifics unstated, so an agent would need to infer too much from the schema.

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%, so the description must carry parameter meaning. It loosely maps functions to 'complete analyze_function Evidence records' and implies start/goal are canonical addresses, but does not explain the required relationship between them, constraints, or what each parameter individually controls.

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 and resource: 'Build every shortest direct-callee path' from 'complete analyze_function Evidence records' using 'exact canonical addresses.' This is much more specific than a generic build tool and distinguishes the operation from analyze_function by consuming its Evidence rather than performing analysis.

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?

The prerequisite is implied: the tool expects complete analyze_function Evidence records. It also notes that missing dossiers and provider mixing remain unknown, which hints at limitations. However, it does not explicitly say when to use this tool versus siblings like trace_call_path or get_call_graph.

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