Skip to main content
Glama
klodr

mercury-invoicing-mcp

mercury_create_customer

Create a new Accounts Receivable customer to onboard them before issuing invoices. Returns a customer ID required by the invoice creation tool. Check existing customers first to avoid duplicates.

Instructions

Create a new Accounts Receivable customer (a billable entity you will later invoice).

USE WHEN: onboarding a new customer before issuing them an invoice. The returned id is what mercury_create_invoice expects as customerId.

DO NOT USE: for payment recipients (use mercury_add_recipient — different surface, used for outbound bank transfers, not invoicing).

SIDE EFFECTS: writes a new customer to your Mercury workspace. Persistent. NOT idempotent at the API level — calling twice with the same payload creates two customers; check mercury_list_customers for existing entries before creating to avoid duplicates.

RETURNS: { id, name, email, address, ... } — keep id for the invoicing tools.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesCustomer name
emailYesCustomer email
addressNoCustomer billing address (Mercury requires `name` in the address)
Behavior4/5

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

With no annotations provided, the description carries the full burden. It discloses that the tool writes persistent data, is not idempotent, and warns about duplicate creation. While it doesn't cover auth or rate limits, the given information is sufficient for safe usage.

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 concise and well-structured with clear sections: PURPOSE, USE WHEN, DO NOT USE, SIDE EFFECTS, RETURNS. Every sentence serves a purpose without unnecessary verbosity.

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 no output schema, the description includes a RETURNS line with example fields. It covers purpose, usage, side effects, and output comprehensively. The tool's complexity (3 params, nested objects) is adequately handled.

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%, so the schema already describes parameters. The description adds value by explaining the returned `id` is used for invoicing and mentions the address object's `name` requirement, but this is marginal. Baseline 3 is appropriate.

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 starts with a specific verb and resource: 'Create a new Accounts Receivable customer (a billable entity you will later invoice).' It clearly distinguishes from sibling tools by mentioning the difference from mercury_add_recipient, which is for payment recipients.

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. It states when to use (onboarding a customer before invoicing), when not to use (for payment recipients), and references the alternative tool (mercury_add_recipient). It also advises checking for duplicates using mercury_list_customers.

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