Skip to main content
Glama

Report payout outcome

report_payout_outcome

After sending a payout that was checked with validate_payout_beneficiary, report whether it was paid or bounced. Improves future checks.

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

Input Schema

NameRequiredDescriptionDefault
reasonNoOptional bank rejection reason
outcomeYes
request_idYesrequest_id returned by validate_payout_beneficiary

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations declare readOnlyHint=false, openWorldHint=false, and idempotentHint=false, so the agent already knows this writes to a closed system. The description adds useful context by explaining the report feeds back into future checks and is tied to a prior validate_payout_beneficiary request_id. It does not say whether repeated reports are accepted or rejected, whether the outcome is immutable once sent, or what happens with an unknown request_id — gaps that matter given idempotentHint=false.

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?

Two short sentences, with the triggering condition front-loaded before the effect. 'Improves future checks' is the only slightly vague phrase, but it earns its place by explaining why the agent should bother reporting.

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?

There is no output schema and only three simple parameters, so not much is required. Still, a write tool marked non-idempotent should say whether re-reporting the same request_id is safe and when the optional reason should be supplied. As written, an agent could plausibly call it correctly but could also misuse the reason field or double-report.

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 description coverage is 67%, and the description supplies the key semantic link for request_id by tying it to validate_payout_beneficiary output, plus it maps the outcome values to paid/bounced. The optional reason parameter is not mentioned at all, so an agent gets no guidance on when a rejection reason is expected. Better than baseline because of the cross-tool request_id explanation.

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?

States a specific verb and resource: reporting a payout outcome as paid or bounced. It also frames the tool as the closing half of a two-step flow with validate_payout_beneficiary, which separates it from the validate siblings. It stops short of naming validate_payout_batch as a different path, but the core action is unambiguous.

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?

The description gives a clear precondition: use it after sending a payout that was checked with validate_payout_beneficiary. That implies it should not be used for unvalidated payouts or as a validator itself. It does not say what to do if the payout is still pending or how soon after sending to report, so the guidance is contextual rather than exhaustive.

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