Skip to main content
Glama

Designed Word Report

archive_report_document
Read-only

Create a designed, full-colour Word (.docx) report from Colour Memory records. Builds a document, report, write-up, handout or Word file from archive findings. Records are passed by the record_id or slug exactly as archive_search (or another tool) returned them, grouped into sections with a heading and optional narrative. Colour Memory resolves every record itself and draws its name, date, place, notes, evidence grade and source from the archive: no evidence field is accepted from the caller, and an unknown or ambiguous reference refuses the whole document (REPORT_RECORD_NOT_RESOLVED). Colour is shown honestly: a filled chip only where the record has a hex, always with where that hex comes from; otherwise the colour appears as the source's own words in an empty frame. Caller-supplied narrative is printed in blocks labelled as interpretation, never as archive evidence. Returns a signed, time-limited download link (delivery='url', default) or the file inline (delivery='base64'). Limits: 8 sections, 6 records per section.

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": {
      "title": "<title>",
      "sections": "<sections>"
    },
    "name": "archive_report_document"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleYesDocument title, under 90 characters.
deliveryNourl (default) or base64.
sectionsYesOrdered sections of the report.
subtitleNoOne-sentence subtitle.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. Added

TDQS

A4.1/5.0
Behavior5/5

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

Annotations supply only readOnlyHint=true, so the description carries the rest and does it well: it discloses the refusal mode (unknown or ambiguous reference aborts the whole document with REPORT_RECORD_NOT_RESOLVED), that no caller evidence field is accepted, how colour is rendered honestly with provenance, that narrative is labelled interpretation, and the delivery modes. It also states hard limits of 8 sections and 6 records per section, which an agent needs before constructing input.

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 artifact, then constraints, then output and limits — a sensible order with no filler sentences. The one wasteful clause is the synonym string 'Builds a document, report, write-up, handout or Word file', which reads as keyword padding rather than information.

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?

An output schema exists, so return values need not be explained, yet the description still tells the agent that it receives a signed, time-limited link by default or inline base64 on request. Combined with the resolution-failure behavior and the section/record caps, an agent has everything required to call this correctly on the first attempt.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning: record values must be record_id or slug exactly as returned, sections are ordered with heading plus optional narrative, and narrative is printed as labelled interpretation rather than evidence. The default delivery='url' is also restated usefully. The keyword list ('document, report, write-up, handout') adds no semantic value.

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 opening sentence names a specific verb and artifact: 'Create a designed, full-colour Word (.docx) report from Colour Memory records.' That is far more precise than a tautology. It does not, however, differentiate itself from the sibling archive_report_brief, which an agent would plausibly weigh against it, so it stops short of a 5.

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 description tells the caller to pass records 'exactly as archive_search (or another tool) returned them', which sketches a workflow but never says when to choose this over archive_report_brief or brand_report. There are no explicit exclusions or prerequisites beyond the record-resolution rule.

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.

Resources