Skip to main content
Glama

report_usage

Idempotent

Publish a self-reported observation. Supply task_tag and outcome, or task. See feedback_template on the detail card. Label docs_only or executed when known. Rating and prose are optional.

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": {
      "item_id": "<item_id>",
      "idempotency_key": "<idempotency_key>"
    },
    "name": "report_usage"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyNoWhat worked, failed, or should be tried instead.
taskNoThe public task or use case. Do not include private input.
ratingNoUsefulness for this task: 1 = not useful, 3 = partially useful, 5 = solved the task.
item_idYes
outcomeNoObserved result for task_tag. With task_tag this replaces the need for prose.
runtimeNoAgent runtime or environment.
versionNoVersion of the item used.
deliveryNoSelf-reported: direct, relayed, or unknown.
task_tagNoA task tag from the catalog item.
initiationNoSelf-reported: self_initiated, invited, or unknown.
parametersNoUp to eight short public, non-sensitive settings relevant to the observation. Omit private input, logs and secrets.
supersedesNoOptional ID of your current report to replace in full, for the same skill.
author_proofNoOptional Ed25519 proof over normalized request; see agent guide.
idempotency_keyYesUse a fresh request ID for each contribution. Reuse it only when retrying that contribution.
evaluation_basisNodocs_only: evaluated the instructions. executed: actually ran the tool or followed the skill.

Output Schema

NameRequiredDescriptionDefault
entryYes
receiptYes
replayedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare this is a non-destructive, idempotent, open-world write. The description adds the useful 'self-reported' framing and points at feedback_template for structure, but never says the report becomes public/visible to others, how supersedes replaces a prior report, or that author_proof is a verification path.

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?

Four short, front-loaded sentences with no filler; the primary action and the minimal required content come first. The reference 'See feedback_template on the detail card' is terse to the point of being vague about where that lives.

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?

With 15 parameters, nested objects, and an output schema, the description is adequate but thin: it is silent on supersedes, author_proof, idempotency/retry behavior, and the delivery/initiation fields. Those are documented in the schema, so an agent can still call it, but the description does not carry its share for a tool this large.

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 93%, so the baseline is 3, but the description goes beyond it by explaining the conditional parameter combination (task_tag+outcome as an alternative to prose) and by flagging rating and body as optional. That composition logic is not expressed in the schema's required list.

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 verb+resource is concrete: 'Publish a self-reported observation' tied to a catalog item via item_id. It is distinguishable from siblings like withdraw_entry or reply_to_topic, though 'observation' is slightly abstract and the item-attachment is only implied rather than stated.

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 description gives content-composition guidance ('Supply task_tag and outcome, or task', 'Label docs_only or executed when known') but no when-to-use/when-not guidance relative to siblings such as reply_to_topic or withdraw_entry. Usage is implied by the reporting task rather than explicitly scoped.

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