Skip to main content
Glama
klodr

mercury-invoicing-mcp

mercury_request_send_money

Create a pending approval request to send money to a recipient, requiring human sign-off before any funds are transferred. Use for outbound payments that need audit and compliance, ensuring safety and approval before execution.

Instructions

Request to send money — Mercury creates a pending approval request that a human must approve before any funds move. ALWAYS creates an approval request, regardless of workspace policy.

USE WHEN: submitting an outbound payment that should always wait for human sign-off — for safety, audit, or because workspace policy demands it. Pairs naturally with the "submit, then wait for approver" workflow.

DO NOT USE: when you intend to transfer between your own accounts (use mercury_create_internal_transfer — no external recipient). For payments that may execute immediately under workspace policy, use mercury_send_money (different surface).

SIDE EFFECTS: creates a pending approval request on Mercury — no money has moved at this point. A human approver must sign off in the Mercury web/mobile app. Once approved, Mercury executes the underlying ACH / wire / check. Idempotent via idempotencyKey — auto-generated if not passed. Audit log entry on Mercury for the request itself.

RETURNS: { id, status: "pendingApproval", amount, ... } — track via mercury_get_transaction once executed.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
accountIdYesSource Mercury account ID
recipientIdYesRecipient ID
amountYesAmount in USD
paymentMethodYesPayment method
noteNo
externalMemoNo
idempotencyKeyNo
Behavior5/5

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

The description fully discloses that it always creates a pending approval request, no money moves until human approval, and that it is idempotent via idempotencyKey. It also mentions audit log entries, providing comprehensive behavioral detail beyond any hypothetical annotations.

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 well-structured with clear sections (USE WHEN, DO NOT USE, SIDE EFFECTS, RETURNS). Every sentence adds value without redundancy, making it efficient and front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (7 params, approval workflow, no output schema), the description covers purpose, usage, side effects, and return structure. It mentions tracking via `mercury_get_transaction` and the critical 'always pending approval' constraint, leaving no major gaps.

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 57% (4/7 parameters described). The description adds value for `idempotencyKey` by stating it is auto-generated if not passed, but does not describe `note` or `externalMemo`. Thus it partially compensates but leaves gaps for those optional parameters.

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 specifies 'Request to send money — Mercury creates a pending approval request', clearly stating the verb and resource. It distinguishes from siblings like `mercury_send_money` and `mercury_create_internal_transfer`, making the purpose unambiguous.

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 'USE WHEN' and 'DO NOT USE' sections provide clear guidance on when to use this tool versus `mercury_send_money` or `mercury_create_internal_transfer`. Alternatives are named, and context is given for safe delay vs immediate execution.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/klodr/mercury-invoicing-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server