Skip to main content
Glama

create_invoice

Create a new invoice for receiving payments. Generates a payment link that can be shared. Requires authentication.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "create_invoice"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations present, the description carries the full burden; it does disclose two useful traits — that creation produces a shareable payment link and that authentication is required. It says nothing about side effects, idempotency, error behavior, or what state the invoice starts in, which are meaningful gaps for a mutation tool.

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

Conciseness4/5

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

Three short sentences, front-loaded with the action and outcome, with zero filler. It is efficient, though the final sentence could be merged without loss.

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

Completeness3/5

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

For a zero-parameter mutation with no annotations and no output schema, the definition covers purpose, authentication, and one returned artifact. It leaves open what the response contains (invoice ID, link, status), whether repeated calls create duplicates, and how it relates to the invoice-listing and payment tools.

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

Parameters4/5

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

The tool takes zero parameters, so there is no schema semantics to compensate for; baseline 4 applies. The description correctly implies nothing is supplied at call time beyond the authenticated identity.

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

Purpose4/5

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

States a specific verb and resource ('Create a new invoice') plus the intent ('for receiving payments') and the resulting artifact ('payment link'). It is clearly distinct from read operations like list_invoices, but it does not differentiate itself from the write-side siblings such as create_payment or create_commerce_quote.

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

Usage Guidelines3/5

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

'For receiving payments' implies the context of use, but there is no explicit when-to-use versus when-not-to-use framing and no pointer to alternatives like create_payment or get_payment_quote. The agent must infer selection from the name and one phrase.

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.

Resources