Skip to main content
Glama
CSOAI-ORG

Agent Commerce Payments MCP

create_invoice

Create a detailed invoice with line items, tax calculation, fees, and payment terms to process payments.

Instructions

Create a detailed invoice with line items, tax calculation, fees, and payment terms.

Behavior: This tool generates structured output without modifying external systems. Output is deterministic for identical inputs. No side effects. Free tier: 10/day rate limit. Pro tier: unlimited. No authentication required for basic usage.

When to use: Use this tool when you need structured analysis or classification of inputs against established frameworks or standards.

When NOT to use: Not suitable for real-time production decision-making without human review of results.

Args: from_agent (str): The from agent to analyze or process. to_agent (str): The to agent to analyze or process. amount (float): The amount to analyze or process. currency (str): The currency to analyze or process. description (str): The description to analyze or process. line_items (list): The line items to analyze or process. due_days (int): The due days to analyze or process. api_key (str): The api key to analyze or process.

Behavioral Transparency: - Side Effects: This tool is read-only and produces no side effects. It does not modify any external state, databases, or files. All output is computed in-memory and returned directly to the caller. - Authentication: No authentication required for basic usage. Pro/Enterprise tiers require a valid MEOK API key passed via the MEOK_API_KEY environment variable. - Rate Limits: Free tier: 10 calls/day. Pro tier: unlimited. Rate limit headers are included in responses (X-RateLimit-Remaining, X-RateLimit-Reset). - Error Handling: Returns structured error objects with 'error' key on failure. Never raises unhandled exceptions. Invalid inputs return descriptive validation errors. - Idempotency: Fully idempotent — calling with the same inputs always produces the same output. Safe to retry on timeout or transient failure. - Data Privacy: No input data is stored, logged, or transmitted to external services. All processing happens locally within the MCP server process.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
amountYes
api_keyNo
currencyNoGBP
due_daysNo
to_agentYes
from_agentYes
line_itemsNo
descriptionNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior1/5

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

The description internally contradicts itself: it claims to create an invoice but also states it is read-only with no side effects. This is a serious inconsistency that misleads the agent about the tool's true behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is lengthy and repetitive, with the 'Behavioral Transparency' section echoing information already in 'Behavior'. It lacks front-loading and contains irrelevant generic content.

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

Completeness2/5

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

Despite providing details on rate limits and error handling, the description fails to explain the actual invoice creation process, output format, or side effects, leaving critical gaps for a tool that claims to create an invoice.

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

Parameters1/5

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

All parameter descriptions in the 'Args' section are generic placeholders ('The X to analyze or process') that do not add any meaning beyond the parameter names, offering zero value given 0% schema coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description initially states 'Create a detailed invoice', which matches the name, but later contradicts it by claiming the tool is read-only and produces no side effects, undermining purpose clarity.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

The 'When to use' section suggests using the tool for structured analysis or classification, which is not aligned with invoice creation, and fails to differentiate from siblings like process_payment or release_escrow.

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/CSOAI-ORG/agent-commerce-payments-mcp'

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