Skip to main content
Glama
Sign In
pay-mcp

pay-mcp

by MonadWorks
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

pay_request

Generate a payment request link so others can send you USDC. Set the amount and optional memo to receive payments directly.

Instructions

Generate a payment request. Creates a payment link that others can use to send you USDC.

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>"
    },
    "name": "pay_request"
  }
}

Input Schema

NameRequiredDescriptionDefault
memoNoOptional description for this payment request
amountYesAmount to request in USDC (e.g., "25.00")

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of disclosing behavioral traits. It only mentions generating a link and does not state whether authentication is required, if the link expires, if there are fees, or what side effects occur (e.g., saved to history). For a mutation tool, this is a significant gap.

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?

The description is exactly two sentences, front-loaded with the core purpose, and contains no redundant information. Every word earns its place.

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?

Given the tool's simplicity (2 simple params, no output schema), the description covers the main functionality and implies the return value (the payment link). It could be improved by explicitly stating that the link is returned and whether it is saved, but it is sufficient for a straightforward tool.

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 coverage is 100%, with both 'amount' and 'memo' described. The description adds no parameter-specific meaning beyond the schema, so the baseline of 3 applies. It does not elaborate on format nuances or additional context.

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 clearly states the tool's function: generating a payment request that creates a link for others to send USDC. The verb 'generate' and resource 'payment request' are specific, and the distinction from siblings (pay_balance, pay_send, pay_history) is apparent.

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 provides clear context: this tool is for receiving USDC via a payment link, which implies use when you want to request payment. It does not explicitly exclude alternatives, but the sibling names make the differentiation obvious, falling just short of explicit 'when-not' guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools