Skip to main content
Glama

Maple Minute

Get a payment link

get_payment_link

A fresh Stripe checkout link for an unpaid company, for a person to pay.

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>"
    },
    "name": "get_payment_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesCompany id like MM-12, from list_companies.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations declare readOnlyHint=false and destructiveHint=false, so the description must explain the side effect it hints at; 'fresh' suggests a new checkout link is minted on each call, implying repeated calls produce different links, but this is never stated. It omits whether prior links are invalidated, whether expiry applies, and what happens against an already-paid company.

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?

A single tight sentence with the precondition front-loaded and no filler. It reads as a noun phrase rather than a complete clause, which costs a little clarity, but nothing is wasteful.

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 one-parameter tool with full schema coverage and annotations present, the description covers the essential premise but leaves out behavior an agent would want: side-effect nature of link creation, validity period, and error conditions. Adequate but with clear gaps for an operation that creates external Stripe state.

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% and the single parameter already documents the expected format (MM-12) and its source (list_companies), so the baseline of 3 applies. The description adds no further meaning about the id beyond what the schema states.

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?

The description identifies a specific resource (a Stripe checkout link) and scope (an unpaid company, meant for a person to pay), which is more precise than the title's generic 'Get a payment link'. It stops short of an explicit verb, so whether the call merely retrieves an existing link or generates a new one is only hinted at by the word 'fresh'.

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?

The phrase 'for an unpaid company' supplies a precondition an agent can act on, and 'for a person to pay' clarifies the intended recipient. There is no explicit when-not guidance, no statement about what to do if the company is already paid, and no pointer to a sibling for alternate paths.

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