Skip to main content
Glama

record_outcome

Capture a task outcome and link it to the revisions used, with optional notes, task label, actor, and idempotency key for traceable provenance.

Instructions

Record a task outcome linked to revisions you used.

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": {
      "outcome": "<outcome>"
    },
    "name": "record_outcome"
  }
}

Input Schema

NameRequiredDescriptionDefault
notesNo
outcomeYes
task_labelNo
actor_handleNo
revision_idsNo
idempotency_keyNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description must carry the full behavioral burden. It says "Record," implying a mutation, but does not disclose permissions, whether records are immutable or reversible, how idempotency works, or what side effects occur. This is a significant transparency gap for a write-style tool with six parameters.

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 definition is a single front-loaded sentence with no wasted wording. Its brevity is structurally clean, though the compactness also contributes to under-specification elsewhere. It is appropriately concise but not rich.

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 mutation-style tool with six parameters, 0% schema description coverage, and no annotations. Although an output schema exists and therefore return values need less explanation, the description still leaves nearly all input semantics and behavioral expectations undocumented. It is not complete enough for an agent to invoke confidently.

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%, so the description needs to compensate for all six undocumented parameters. It mentions the outcome and links to revisions, loosely mapping to outcome and revision_ids, but gives no meaning for notes, task_label, actor_handle, or idempotency_key. The added semantic value is therefore minimal.

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 provides a specific verb and resource: "Record a task outcome." It also scopes the record to revisions the caller used, which gives useful purpose context. It does not clearly distinguish this tool from the sibling "record" tool, so it falls short of the top score.

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?

The phrase "linked to revisions you used" implies the tool is relevant after using revisions and wanting to record an outcome. However, it gives no explicit when-to-use guidance, no exclusions, and no comparison with alternatives such as record or propose_revision. Usage is therefore inferable but under-specified.

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