Skip to main content
Glama

Outil.io

Create quote payment link

create_quote_payment_link

Devis accepté : lien de paiement Stripe pour l’acompte (deposit), le solde (balance) ou le total (full). Le paiement confirmé crée la transaction et met à jour paidAmount. Exige l’encaissement activé (get_payment_onboarding_status).

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": "create_quote_payment_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
partNobalance

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Beyond the annotations (readOnlyHint=false, openWorldHint=true), the description discloses the downstream side effect: a confirmed payment creates the transaction and updates paidAmount. It also discloses the onboarding prerequisite. It doesn't say whether the link expires or is single-use, which would complete the behavioral picture.

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 resource and scope, then the side effect, then the prerequisite. No filler; only the missing return-value mention keeps it from being optimal for its length.

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

Completeness4/5

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

For a 2-parameter mutation with annotations and no output schema, the definition covers scope, side effects and prerequisites. The one notable omission is that it never says the tool returns the payment link/URL itself, which is the primary artifact an agent would need.

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 description coverage is 0%, so the description must carry the load. It does explain the meaning of the 'part' enum values (deposit/balance/full), but never clarifies that 'id' is the quote identifier, nor mentions the default of 'balance'. Partial compensation for a real gap.

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 states a specific verb and resource ('lien de paiement Stripe' for an accepted quote) and enumerates the scope (acompte/solde/total), which an agent can distinguish from create_payment_page or send_quote. It is clear what is created, though it doesn't explicitly contrast itself with the other payment-link siblings.

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

Usage Guidelines4/5

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

It gives a precondition ('Devis accepté') and a hard requirement ('Exige l'encaissement activé') and points to get_payment_onboarding_status as the gate check. It lacks explicit when-not-to-use guidance (e.g. unpaid/non-accepted quotes, or when to pick this over create_payment_page), so it stops short of a 5.

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.