Skip to main content
Glama

create_sales_payment_link

Idempotent

Create a customer payment link. The amount is before tax in minor units. Reuse the same ID and details on retry.

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": {
      "id": "<id>",
      "title": "<title>",
      "amount": "<amount>",
      "taxRate": "<taxRate>",
      "seller": "<seller>"
    },
    "name": "create_sales_payment_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
titleYes
amountYes
sellerYes
taxRateYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false and idempotentHint=true, but the description earns credit for making idempotency actionable: reuse the same ID and details on retry. It stays silent on auth requirements, link expiry, and what the created entity contains, and it never states what is returned, which matters for a tool whose whole point is producing a link.

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?

Three short sentences, each carrying a distinct fact: what it does, the unit convention for the most error-prone field, and retry behavior. No filler and no repetition of the schema.

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?

A mutation tool with five required params, a nested seller object, 0% schema coverage and no output schema needs the description to explain taxRate's discrete values and the shape of the result. It covers amount and id but omits both, leaving real risk of an agent guessing 10 vs 1000 or misconstruing the seller fields.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must carry the load. It clarifies the two most dangerous params well (amount is pre-tax in minor units; id is the reuse key on retry), but leaves taxRate's anyOf of const 0 or const 1000 completely unexplained, and says nothing about title or the nested seller object with its required name/email and optional abn/address. Half the surface remains opaque.

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?

"Create a customer payment link" names a specific verb and resource, so the agent knows exactly what artifact this produces. It does not distinguish itself from siblings such as create_invoice_draft or record_invoice_payment, so an agent choosing between payment-recording tools gets no routing help.

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?

There is no statement of when to prefer this tool over creating an invoice or recording a payment directly, nor any prerequisite or exclusion. The only usage-adjacent sentence is the retry instruction, which addresses repeated invocation rather than tool selection.

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