Skip to main content
Glama
Sign In
TraceDelta

TraceDelta

by swaroop2005
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

drill_down

Retrieve bounded raw evidence behind a reference from an evidence capsule, with field limits and redaction. Reports estimated source bytes examined for cost transparency.

Instructions

Retrieve the bounded raw evidence behind a reference (redacted, field-limited). This is the explicit cost path; the response reports estimated source bytes examined.

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": {
      "capsule_id": "<capsule_id>",
      "evidence_id": "<evidence_id>"
    },
    "name": "drill_down"
  }
}

Input Schema

NameRequiredDescriptionDefault
fieldsNo
consumerNo
capsule_idYes
evidence_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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 provided, the description carries the behavioral burden. It discloses that results are redacted and field-limited, and that the response reports estimated source bytes examined (cost transparency). However, it doesn't mention auth needs, rate limits, or what happens on failure. The description adds meaningful value but leaves gaps for a cost-path tool.

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?

Two sentences, compact and front-loaded with the core purpose first. The second sentence about cost-path reporting is relevant. No wasted words, though the dense jargon ('bounded raw evidence', 'capsule') hurts accessibility slightly.

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 a tool with 0% schema coverage, no annotations, no output schema, and 4 parameters (2 undocumented by any prose and only structurally named in schema), the description is too thin. It doesn't explain return format, how fields filtering works, or resolution mechanics. The cost-path framing is useful but insufficient for reliable tool selection and invocation.

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 compensate. It gives zero parameter information beyond the schema: fields, consumer, capsule_id, evidence_id are all unexplained in prose. The description doesn't clarify what 'fields' restricts, what a 'consumer' represents, or relationship between capsule_id and evidence_id.

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

Purpose3/5

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

The description states it retrieves 'bounded raw evidence behind a reference (redacted, field-limited)', giving a specific verb+resource. However, the term 'reference' and 'capsule' are domain jargon not defined, and it doesn't clearly differentiate from get_capsule or find_related_capsules siblings. It does add the distinguishing cost-path detail.

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 phrase 'explicit cost path' implies it should be used when cost matters, but no explicit when-to-use or when-not-to-use guidance is given. It doesn't mention alternatives or exclusions. The guidance is implied rather than stated explicitly.

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