Skip to main content
Glama

record_utterances

Stores engineer prompts verbatim for the Worktrail prompt uploader, keyed by source_ref IDs, and ignores re-sent IDs. Use it only in the thin client, not for agents.

Instructions

For the Worktrail prompt uploader only (thin client) — not for agents. Stores the engineer's prompts verbatim, keyed by the prompt id the hook gave as source_ref; re-sent ids are ignored.

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": {
      "items": "<items>"
    },
    "name": "record_utterances"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description must carry the whole load; it does disclose two key traits: storage is verbatim and duplicate ids are silently ignored (idempotent). It omits permissions, error behavior, and what happens to malformed items, so the behavioral picture is partial.

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?

One sentence with the audience restriction front-loaded and the key semantics (verbatim, source_ref key, duplicate suppression) following. Dense but every clause carries information; only minor loss from packing three ideas into one sentence.

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

Completeness3/5

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

For a single opaque-array parameter with no output schema and no annotations, the definition covers audience, key field, and idempotency, but leaves the item structure and failure behavior undocumented, which is a meaningful gap for an untyped array.

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?

The single parameter is an untyped item array at 0% schema coverage. The description adds real meaning by naming source_ref as the key field and implying prompt text is the payload, but it never describes the per-item shape or required fields within items.

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 action (stores prompts verbatim, keyed by prompt id from source_ref) and explicitly scopes it to the Worktrail prompt uploader. It does not distinguish itself from siblings like add_utterance or note_turn, but the 'not for agents' framing carves out its audience clearly.

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

Usage Guidelines4/5

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

Gives an explicit negative routing rule ('not for agents') and identifies the sole legitimate caller (thin Worktrail client). It does not name which sibling an agent should use instead, so the exclusion is stated without a redirect.

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