Skip to main content
Glama

MARU Japan Hands

Ask the wallet owner to approve a payment

maru_wallet_request_payment

File a payment request in the user's MARU wallet. This does NOT pay. The user sees the amount and recipient in the MARU app and approves with Face ID or rejects. Use maru_wallet_request_status to see the outcome. Never tell the user a payment was made until the status is 'done'.

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>",
      "chain": "<chain>",
      "to": "<to>",
      "amount_jpyc": "<amount_jpyc>",
      "title": "<title>"
    },
    "name": "maru_wallet_request_payment"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesRecipient address (0x…)
chainYes
titleYesWhat this payment is for, in the user's language, max 80 characters
detailNo
agent_tokenYes
amount_jpycYesWhole JPYC (1 JPYC = 1 JPY)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations cover the safety profile (readOnlyHint=false, destructiveHint=false, openWorldHint=false), and the description usefully adds the human-in-the-loop behavior: the request is visible in the app and can be approved via Face ID or rejected. It does not address the non-idempotent flag, i.e. whether repeat calls create duplicate requests, nor any auth expectations for agent_token — a meaningful gap for a request-creating tool.

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?

Four short sentences, front-loaded with the action and the negative scope, then the user-facing behavior, then the follow-up tool and the guardrail. No filler and every sentence carries a distinct instruction.

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 six-parameter, non-idempotent request tool with no output schema, the description covers the lifecycle and the follow-up call well. The remaining gap is the return value — there is no output schema and the description never says a request identifier comes back, which the agent would need to call maru_wallet_request_status.

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 only 50%, and the description adds essentially nothing about parameters — it merely restates that the user sees 'the amount and recipient.' The undocumented parameters (chain, detail, agent_token) get no clarification of allowed values, format, or role, so the description fails to compensate for the coverage gap.

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?

States a specific verb and resource ('File a payment request in the user's MARU wallet') and immediately scopes it negatively ('This does NOT pay'), which is exactly the distinction an agent needs. It also names the sibling that resolves the outcome, so it is separable from maru_wallet_request_status without opening either schema.

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?

Gives explicit when-to-use context (the user approves in-app), names the follow-up tool ('Use maru_wallet_request_status to see the outcome'), and includes an operational rule ('Never tell the user a payment was made until the status is done'). That is routing guidance plus a guardrail, not just implied usage.

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.