Skip to main content
Glama

Trace Feature

trace_feature

Trace a literal query across matching strings and procedures, their cross-references, and containing-procedure resolution, returning observations, operation counts, and residual unknowns.

Instructions

Trace the complete literal query, preserving spaces, through every matching string and procedure, their xrefs, and truthful containing-procedure resolution. Returns observations, operation count, and residual unknowns without inferring reference kinds.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "license",
      "case_sensitive": false
    },
    "name": "trace_feature"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesNon-empty feature or text query to investigate.
case_sensitiveNoWhether text matching distinguishes uppercase and lowercase.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

The description adds real behavior beyond annotations by naming the return payload (observations, operation count, residual unknowns) and stating a deliberate limitation: it does not infer reference kinds. However, annotations declare readOnlyHint=false and idempotentHint=false, and the description never explains why a trace mutates state or whether repeat calls differ, leaving that discrepancy unaddressed rather than contradicted.

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?

Two sentences with no filler, and the return contents are front-loaded in the second sentence. The first sentence, however, is a dense run-on of undefined jargon ('truthful containing-procedure resolution') that costs clarity without earning compactness.

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?

With no output schema, the description does carry the burden of describing results, and it does so at a high level. But for a tool whose annotations mark it neither read-only nor idempotent, the definition never says what state changes occur, how large the operation count can get, or when to prefer a sibling, so it is only minimally complete.

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%, so both query and case_sensitive are already documented in the schema. The description only reinforces the query semantics with 'complete literal query, preserving spaces,' adding little beyond what the schema's 'Non-empty feature or text query' already conveys. Baseline 3 applies.

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 has a specific verb (trace) and a clearly bounded resource: a complete literal query, preserving spaces, followed through matching strings, procedures, and their xrefs. Phrases like 'truthful containing-procedure resolution' and 'without inferring reference kinds' are obscure, but the core action is distinguishable from siblings such as xrefs or trace_call_path.

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?

There is no explicit when-to-use guidance and no named alternative among the many trace_* siblings. The agent must infer from the single word 'literal' (with spaces preserved) that this is for text/string hunting rather than call-path or reference-kind tracing, which is a thin basis for tool selection.

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