Skip to main content
Glama

SCRIPTMASTERLABS — GatePay

GatePay Payout Quote

gatepay_quote
Read-onlyIdempotent

Quote a payout: runs the same policy evaluation POST /v1/route would, returning allow/deny, the reasons and the fee split. Settles NOTHING and writes NO ledger entry.

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": {
      "amount": "<amount>",
      "destination": "<destination>"
    },
    "name": "gatepay_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
memoNoOptional memo recorded with the request payload.
amountYesAmount in USDC.
destinationYesDestination wallet address on Arc.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint, so the safety profile is covered by structured data and the "settles nothing / writes no ledger" line largely restates it. The description does add real value by naming the response contents (allow/deny verdict, reasons, fee split), which no output schema provides, but it says nothing about rate limits, latency, or whether quotes expire.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, zero filler, with the core action front-loaded and the critical non-effect statement placed last for emphasis. Capitalized negation is used sparingly and effectively rather than as noise.

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 three-parameter read-only quote tool with no output schema, the description covers the essential ground: what it evaluates, what it returns, and that it has no side effects. Minor gaps remain around quote validity window and whether the fee split is informational only, but nothing needed to call it correctly is missing.

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%: amount (USDC, exclusiveMinimum 0), destination (Arc wallet address), and memo are all documented in the schema itself. The description adds no parameter-level detail such as formatting rules for addresses or the significance of the memo field, so the baseline 3 applies.

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?

"Quote a payout" gives a specific verb plus resource, and the sentence spells out what the call actually does: it runs the same policy evaluation as POST /v1/route and returns allow/deny, reasons, and fee split. The contrast with the routing path is clear, though the sibling is referenced as an HTTP endpoint rather than by its tool name, so differentiation relies on the agent mapping /v1/route to gatepay_route.

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?

"Settles NOTHING and writes NO ledger entry" establishes a clear dry-run/preview context that tells an agent when this is the safe choice over actually routing funds. There is no explicit exclusion statement naming gatepay_route or gatepay_status, so the when-not guidance is inferred rather than stated.

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