Skip to main content
Glama

Last Price

report_outcome

Report whether a price from compute_price was used: once the buyer has accepted or turned down a price, report it. Pass receipt.id from that result as usage_event_id, or omit it to report the last price compute_price returned on this connection or tools instance, once (the hosted MCP endpoint remembers nothing, so pass it there). Outcomes are what later routing and confidence learn from. With outcome pricing on, a rejection within the call's outcome window gives back part of what it cost; the result says what was refunded. Needs a Last Price credential. Report only what actually happened. Needs a claimed workspace: a sandbox key from self-registration is refused (403) until a person claims the workspace.

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": "report_outcome"
  }
}

Input Schema

NameRequiredDescriptionDefault
outcomeYesWhether the price was used.
evidence_urlNoOptional evidence: an https link to the record.
evidence_noteNoOptional evidence: a short note on why.
quality_scoreNoOptional: how good the price was, 0 to 1.
usage_event_idNoThe usage event of the priced call: receipt.id on the compute_price result. Pass it whenever you priced more than one thing. Omitted, the last compute_price result on this connection is reported, once.
evidence_referenceNoOptional evidence: an order, ticket or invoice id in your own system.

Output Schema

NameRequiredDescriptionDefault
eventNo
messageNoA short sentence about the result that an agent can show its person.
quote_expiredNo
outcome_windowNo
quote_expired_seconds_agoNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / message / description
      Added value: +"A short sentence about the result that an agent can show its person."
  2. Changed2 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "additionalProperties": true,
      +  "properties": {
      +    "event": {
      +      "properties": {
      +        "id": {
      +          "type": "string"
      +        },
      +        "outcome": {
      +          "type": [
      +            "string",
      +            "null"
      +          ]
      +        }
      +      },
      +      "type": "object"
      +    },
      +    "message": {
      +      "type": "string"
      +    },
      +    "outcome_window": {
      +      "type": "object"
      +    },
      +    "quote_expired": {
      +      "type": "boolean"
      +    },
      +    "quote_expired_seconds_ago": {
      +      "type": "number"
      +    }
      +  },
      +  "type": "object"
      +}
  3. Changed2 schema fields changed
    • changedInput schema / properties / usage_event_id / description
      Previous value: -"The usage event of the priced call: receipt.id on the compute_price result."New value: +"The usage event of the priced call: receipt.id on the compute_price result. Pass it whenever you priced more than one thing. Omitted, the last compute_price result on this connection is reported, once."
    • changedInput schema / required
      Previous value: -[
      -  "usage_event_id",
      -  "outcome"
      -]New value: +[
      +  "outcome"
      +]
  4. Added

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the annotations it discloses statelessness of the hosted endpoint ('remembers nothing, so pass it there'), single-shot semantics for the fallback path, the refund mechanic for rejections inside the outcome window, the required Last Price credential, and the 403 refusal for unclaimed sandbox keys. That is substantial behavioral context the annotations do not carry.

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?

Purpose is front-loaded in the first clause and the parentheticals are compact, though the single dense paragraph mixes reporting rules, billing mechanics, and auth constraints. The line 'Report only what actually happened' is the one sentence that adds little.

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

Completeness5/5

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

For a non-idempotent write with an output schema, the description covers everything an agent needs before calling: trigger condition, id resolution, credential and workspace prerequisites, and the consequence of rejection. Return values are delegated to the output schema appropriately.

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 100%, so the baseline is 3, but the description still adds real meaning for usage_event_id by explaining that omission resolves to the last compute_price result and that this only works once and not on the hosted endpoint. Other parameters (evidence fields, quality_score) are left to the schema.

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 opens with a specific verb + resource ('Report whether a price from compute_price was used') and ties the tool to the exact upstream call that produces its input, so an agent can tell it apart from verify_price or get_receipt without opening the schema.

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 clearly ('once the buyer has accepted or turned down a price, report it') and explains the omitted-parameter path versus passing a specific receipt id. No sibling alternative is named as a when-not, 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.

Resources