Skip to main content
Glama

Check an agent before paying it (free)

pay_check
Read-onlyIdempotent

Start here before your agent pays or hires another agent. One free call before your agent pays or hires another: its latest statement (stale, age, chain_ok, flags), live incidents, its detections in the last 72 hours, the token approvals its wallet has given (unlimited ones, and any to a plain account), its last counted payment, and its payments seen after the statement window closed (from its 25 newest payments, so the hours a statement cannot show are not blind). Returns facts and which of the documented refuse conditions are met; the decision stays with you. The paid precheck pack adds what the address you were given to pay is. Not for the address you were given to pay (payee_facts) or for applying your own written policy (gate_check).

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": {
      "agent": "<agent>"
    },
    "name": "pay_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
agentYesAgent token id, slug or bound wallet

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already cover the safety profile (read-only, idempotent, non-destructive), so the description's job is to add context, which it does: it discloses the cost model (one free call, paid pack upsell), the data staleness caveat ("stale, age"), the sampling limitation (post-window payments come only from the 25 newest payments), and that it returns facts only while the decision stays with the caller. Minor tension exists between openWorldHint=false and the claim of "live incidents," but this is a scope nuance rather than a contradiction.

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

Conciseness3/5

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

The content is front-loaded and information-dense, but the opening is redundant: the "before your agent pays or hires another agent" clause appears twice in the first two sentences. The remainder is one long comma-spliced chain of parentheticals, which is harder to scan than a short bulleted list of returned facts would be.

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?

With no output schema, the description carries the full burden of explaining returns, and it does enumerate the returned facts and the freshness limits (72-hour detections, 25-newest-payment window). The only gap is that "the documented refuse conditions" are referenced without being enumerated here, so the agent must infer what those conditions are.

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?

One parameter at 100% schema coverage, so the schema already documents that 'agent' accepts a token id, slug, or bound wallet. The description adds no identifier syntax or resolution guidance beyond that, which is acceptable for a single well-documented parameter.

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 description states a specific action on a specific resource: check an agent's record before paying or hiring it, and enumerates exactly what facts come back (statement staleness, chain_ok, flags, live incidents, 72h detections, token approvals, last counted payment, post-window payments). It also names the siblings it is not (payee_facts, gate_check), so an agent can separate it from neighbors.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit when-to-use: "Start here before your agent pays or hires another agent." Explicit when-not, with the alternative named for each case: payee_facts for the address being paid, gate_check for applying your own written policy. It also flags the free-tier boundary (one free call, paid precheck pack adds payee facts).

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.