Skip to main content
Glama

Trace a record

trace_record
Read-onlyIdempotent

Follow a learning-design record forward and backward through its lifecycle: evidence, needs, objectives, assessments, datasets, metrics, notes, and findings, with each link naming its field.

Instructions

Where a record comes from and where it leads, both ways along the design's lifecycle: evidence and the need it supports, the objective the need generated, the items that assess it, their placements and assessments, and the datasets and metrics measured on them; with the notes and findings written on the records passed. Each link names the field it follows. The answer carries labels: read a note's or a relationship's rationale with get_record.

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": {
      "type": "<type>",
      "id": "<id>"
    },
    "name": "trace_record"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe record's id, as Type/local (LearningObjective/lateral-reading-check) or the local part alone.
refNoA commit id to read at, as an earlier answer named it: pass the commit from your first answer to every follow-up, so the conversation reads one state of the design. Pass this or branch, not both.
typeYesThe record's class, such as LearningObjective, AssessmentItem, Module or DesignNote.
branchNoThe branch to read at its latest commit. Leave out to read the default branch (main unless configured otherwise). Pass this or ref, not both.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds real value beyond them: it discloses that traversal goes in both directions, what record types are included in the result, and that each link names the field it follows. It does not discuss result size, cycles, or truncation, which keeps it short of a 5.

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?

The lead clause ('Where a record comes from and where it leads, both ways along the design's lifecycle') is well front-loaded, but the remainder is one very long semicolon-chained sentence whose enumeration is hard to parse. Every element is arguably useful, but the structure hurts readability.

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?

There is no output schema, so the description carries the burden of describing return values, and it does so by enumerating the record types and relationships returned and noting that links name their field. Given the four-parameter, read-only nature of the tool, this is nearly complete; only result volume or cycle behavior is unaddressed.

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 the schema already explains id, type, ref and branch in detail, including the ref/branch mutual exclusion. The description adds no parameter-level meaning beyond that, so the baseline of 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 names a specific verb (trace) and resource (a record) and scopes it to 'both ways along the design's lifecycle', enumerating the entity chain (evidence, need, objective, items, placements, assessments, datasets, metrics). It also distinguishes itself from get_record for rationale text, so an agent can tell the two apart. The phrasing is dense, but the purpose is unambiguous.

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 by the lifecycle-traversal framing and there is one explicit routing hint: read a note's or relationship's rationale with get_record. However, there is no explicit when-to-use versus compare_record, record_history or what_references, and no stated preconditions. Guidance is present but inferential rather than declarative.

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