Skip to main content
Glama

record

Capture a typed candidate entry—preference, decision, procedure, failure, or similar—in a writable namespace for scoped, provenance-tracked retrieval.

Instructions

Record a typed candidate entry in a namespace you may write.

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": {
      "namespace": "<namespace>",
      "entry": "<entry>"
    },
    "name": "record"
  }
}

Input Schema

NameRequiredDescriptionDefault
entryYes
namespaceYes
actor_handleNo
idempotency_keyNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/5.0
Behavior2/5

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

With no annotations supplied, the description carries the full burden. It does convey two useful facts: writes go into a lifecycle that begins as 'candidate' (not immediately authoritative) and a write-permission constraint exists. Beyond that it says nothing about idempotency behavior, what a duplicate call returns, what revision identity is created, or whether prior state is mutated.

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?

A single short sentence with the scope constraint front-loaded and no filler, so it is concise by construction. But the brevity comes at the cost of specification rather than from efficient encoding of necessary information.

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

Completeness2/5

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

This is a high-complexity write tool with a deep nested payload, four parameters, no annotations, and an output schema. One sentence is not enough: an agent cannot tell what happens to entries not starting from the default lifecycle, how idempotency retries behave, or how namespace authorization failures surface.

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

Parameters2/5

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

Schema description coverage is 0% for the four top-level parameters. The nested $defs are well documented, but the description adds no meaning for 'namespace', 'actor_handle', or 'idempotency_key' — the last of which materially changes call semantics and is left entirely unexplained.

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

Purpose3/5

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

The description states a specific verb ('Record') and resource ('typed candidate entry in a namespace'), which is more than a tautology. However, 'typed candidate entry' is domain jargon that the schema defines via the Kind enum, and the sentence does not distinguish this write path from siblings such as propose_revision or upload_evidence.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no prerequisite statement beyond the vague phrase 'you may write', and no named alternative for the near-identical mutate paths (propose_revision, record). An agent must infer selection criteria entirely from the sibling names.

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