Skip to main content
Glama

inspect

Retrieve one Worktrail record in full by its reference number, such as a decision, constraint, evidence item, or note. Use it to read the complete, unsummarized entry with provenance.

Instructions

Return one record in full by its number (ref), as find, trail and resume print it: D decision · C constraint · R ruled-out · T term · F/O/N focus/open/next declaration (with what superseded it, if anything) · E evidence verbatim with provenance · : a note (what the agent observed and concluded, marked interpretation, with the evidence it cites). evidence_id= still works for evidence. Not summarized.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "inspect"
  }
}

Input Schema

NameRequiredDescriptionDefault
refNo
evidence_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

No annotations exist, so the description carries the full burden, and it does a lot: it enumerates exactly what each ref prefix returns, notes that supersession is included for F/O/N declarations, marks notes as interpretation with cited evidence, and says evidence returns verbatim with provenance. It leaves gaps around error behavior for an unknown ref and what happens when no argument is supplied (both parameters default to null).

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?

Front-loaded with the purpose in the first clause, then a dense middot-delimited legend of record types. The legend is information-bearing rather than filler, though the single run-on sentence is harder to scan than a short structured list would be.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema and no annotations, so the description does the heavy lifting on return shape, and it largely succeeds by spelling out the per-record-type payload and the provenance/interpretation fields. What it omits — invalid-ref behavior and the both-parameters-null case — is minor for a read-only inspector.

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 coverage is 0% — the schema only supplies titles and null defaults — so the description must compensate, and it partially does: ref is defined as the record's number and evidence_id is explained as an alternate way to address evidence. It does not say whether ref accepts prefixed forms (e.g. "D123") or bare ids, nor what happens if both parameters are omitted, so the 0% coverage gap is not fully closed.

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: "Return one record in full by its number (ref)." The phrase "as find, trail and resume print it" ties it to sibling behavior, implying those tools print abbreviated lines while this one prints the full record, and "Not summarized" reinforces that distinction. It stops short of an explicit contrast statement, but an agent can still tell it apart from the listing tools.

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?

Usage is implied rather than stated: the record-type legend and "Not summarized" suggest using this when you need the full body of a single item, but it never says "use find/trail/resume for listings" or when not to use it. The mention of siblings describes their output format, not when to prefer one over this tool.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.