Skip to main content
Glama

InProcess Cockpit

Lien de paiement

lien_paiement

Le lien d'une page de paiement sécurisée d'InProcess (Stripe) pour prendre une offre ou recharger des crédits : la personne l'ouvre et paie sur cette page, aucune donnée de carte ne passe par la conversation. Réservé aux propriétaires de l'organisation.

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

Input Schema

NameRequiredDescriptionDefault
offreNoL'offre à prendre
rythmeNoPaiement mensuel (par défaut) ou annuel
creditsNoOu : un nombre de crédits à recharger

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.9/5.0
Behavior4/5

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

Annotations only say readOnlyHint=false and destructiveHint=false; the description adds genuine context beyond them: payment happens on an external Stripe-hosted page, no card data transits the conversation, and an ownership permission is required. It does not spell out that the tool merely returns a link rather than charging anything itself, which would have closed the loop.

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?

Two sentences, front-loaded with what the link is for before stating the owner-only restriction. The main sentence is dense with a colon-separated gloss, but nothing is truly redundant.

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?

All three parameters are optional and fully documented in the schema, and there is no output schema, so the description need not explain return values. It covers purpose, security posture and authorization; the only gap is not clarifying what happens when neither an offer nor credits is supplied.

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 100%, so the schema already documents offre, rythme and credits including their enums. The description only echoes that either an offer or a credits top-up is involved, adding no syntax or precedence rules beyond the schema (which already marks credits as the alternative).

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 concrete deliverable (the link to a secure InProcess/Stripe payment page) and its two purposes: taking an offer or recharging credits. This is well beyond restating the name, though it never names a sibling such as 'offres' or 'mon_offre' to sharpen the boundary.

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?

Gives clear usage context (to subscribe to an offer or top up credits) and a hard prerequisite (organization owners only). It stops short of explicitly naming alternatives or when-not-to-use cases, so it does not reach 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.

Resources