Skip to main content
Glama

MARU Japan Hands

Check a payment request

maru_wallet_request_status
Read-only

Status of a request made with maru_wallet_request_payment: pending (waiting for the owner), done (paid; includes the transaction link), rejected, or failed.

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_token": "<agent_token>",
      "request_id": "<request_id>"
    },
    "name": "maru_wallet_request_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
request_idYes
agent_tokenYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description goes beyond them by enumerating the four possible states and noting that 'done' returns a transaction link, which is genuinely useful behavioral context. Minor gap: nothing about latency/polling behavior for a 'pending' state.

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?

A single well-formed sentence with the resource scope front-loaded and the status enumeration packed in without waste. Nothing could be removed without losing information.

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 rightly does the work of explaining return values by listing the status states and the transaction link. It is nearly complete for a simple two-parameter read; the only missing piece is any meaning for the required agent_token.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description carries the full burden, yet it explains neither parameter. request_id is only obliquely implied by the phrase 'a request made with...', and the required agent_token is never mentioned at all — a notable gap for an auth-style parameter.

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 names a specific resource ('Status of a request') and scopes it to requests created by maru_wallet_request_payment, which cleanly separates it from the write-side sibling. An agent can tell exactly what this returns 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 Guidelines3/5

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

It implies usage by referencing the creating tool ('a request made with maru_wallet_request_payment'), which hints at the poll-after-request workflow. However, it gives no explicit when-to-use or when-not guidance, and no prerequisite (such as needing a request_id from that prior call) is 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.