Skip to main content
Glama

crashtestyourstrategy

Get dossier (audit trail of past diagnostics)

get_dossier
Read-onlyIdempotent

USE WHEN you want one citable record of the diagnostics you ran, with their gate flags. Every enveloped response is recorded by request_id. Give request_ids from your own responses (compiled chronologically) or last_n for your own most recent entries (API token required). Returns the entries with their gate signals (revision_required + grounding_summary) and a ready-to-cite markdown document; the dossier's own revision_required is true when any listed entry carried a gate flag (it does not know whether you later revised). One entry's full payload and call manifest: get_run. A factual record, never advisory.

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": "get_dossier"
  }
}

Input Schema

NameRequiredDescriptionDefault
last_nNoAlternatively: compile your N most recent entries, 1 or more. Needs an API token; anonymous callers use request_ids. Ignored when request_ids is given.
request_idsNoExplicit request_ids to compile chronologically (take them from previous responses' request_id fields).

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +false
  2. Changed1 schema field changed
    • changedInput schema / properties / last_n / description
      Previous value: -"Alternatively: compile the N most recent recorded entries (ignored when request_ids is given)."New value: +"Alternatively: compile your N most recent entries, 1 or more. Needs an API token; anonymous callers use request_ids. Ignored when request_ids is given."
  3. Changed2 schema fields changed
    • addedInput schema / properties / last_n / description
      Added value: +"Alternatively: compile the N most recent recorded entries (ignored when request_ids is given)."
    • addedInput schema / properties / request_ids / description
      Added value: +"Explicit request_ids to compile chronologically (take them from previous responses' request_id fields)."
  4. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), yet the description still adds real behavior: that every enveloped response is recorded by request_id, that last_n requires an API token while anonymous callers must use request_ids, and that the dossier's own revision_required is true when any listed entry carried a gate flag but cannot know whether you later revised. The closing 'factual record, never advisory' frames output trust appropriately.

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 trigger is front-loaded in the first clause and every sentence carries a distinct fact (selection mode, return contents, gate semantics, sibling routing). It is dense rather than padded, though the parenthetical on revision_required is slightly tangled and costs a little readability.

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

Completeness5/5

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

For a two-optional-parameter read tool with an output schema, the description supplies everything an agent needs: how to select entries, what the response contains, how to interpret the gate flags, and where to go for full payloads. No unexplained prerequisite or ambiguity remains.

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%, and both parameter descriptions already state the chronological compile behavior, the token requirement, and that last_n is ignored when request_ids is supplied. The description largely restates that schema content, so it meets the baseline but adds little new parameter meaning beyond ordering and provenance of the ids.

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

Purpose5/5

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

The definition names a specific verb and artifact — compile one citable record of diagnostics you ran, with their gate flags — and explicitly separates it from the sibling that returns a single run's payload ('One entry's full payload and call manifest: get_run'). An agent can distinguish dossier-vs-run without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It opens with an explicit 'USE WHEN' trigger, names the alternative tool (get_run) and the condition that selects it, and describes the two mutually exclusive selection paths (request_ids vs last_n) including the API-token prerequisite for the latter. Nothing about when to call this is left to inference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.