Skip to main content
Glama

Minerals

Report how it went

report_outcome

Records whether what get_listing returned was used. Applies after get_listing, once the work is done. The curator reads the reports to judge what stays listed. Returns one line that says it was recorded.

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": {
      "ref": "<ref>",
      "result": "<result>"
    },
    "name": "report_outcome"
  }
}

Input Schema

NameRequiredDescriptionDefault
refYesThe ref you were given.
reasonNoIf not used: why, in a few words. Do not include code, file contents or repo names.
resultYes"used" if it went into the work, "not_used" if it did not.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations declare a non-read-only, non-idempotent, non-destructive write, and the description adds real context beyond that: the curator consumes these reports to decide what stays listed, and the call returns a single confirmation line. It does not mention duplicate handling despite idempotentHint=false, but the consequence of the write is well conveyed.

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?

Three short sentences, front-loaded with the action and followed by timing, downstream effect, and return shape. Nothing is padded, though the return-value sentence is the least essential since an agent mostly needs the trigger condition and the write's effect.

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

Completeness4/5

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

For a small three-parameter reporting tool with no output schema, the description covers purpose, timing, downstream consumer, and return behavior. The only meaningful gap is what happens on repeated reports, given the non-idempotent annotation.

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?

Schema description coverage is 100%, so ref, result, and reason are already fully documented in the schema, including the enum values and the caution against code contents. The description adds no additional parameter meaning, which is the expected baseline when the schema does the work.

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

Purpose5/5

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

The description gives a specific verb and resource ("Records whether what get_listing returned was used") and ties it to a named sibling, so it is obviously distinct from get_listing, find_design, offer, and suggest_listing. An agent knows immediately that this is a feedback-signal tool, not a discovery or offering tool.

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?

It states the triggering condition precisely: "Applies after get_listing, once the work is done." That is clear when-to-use guidance. It does not name a when-not or an alternative path (e.g. what to do if the listing was never consulted), which keeps it short of a 5.

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.