Skip to main content
Glama

Outil.io

Start payment onboarding

start_payment_onboarding

Activer l’encaissement du client sans clé à copier (Stripe Connect Express) : renvoie url, lien d’inscription Stripe à transmettre au client (identité, IBAN), et l’état. Déjà actif : url null. Propriétaire ou administrateur. country ISO (FR par défaut).

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

Input Schema

NameRequiredDescriptionDefault
emailNo
forceNoNouveau lien même si l’encaissement est actif (mise à jour des informations)
countryNo
businessNameNo
businessTypeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Beyond the annotations (which only say it is a non-read-only, open-world, non-destructive call), the description discloses the return payload (url, Stripe signup link, state), the already-active edge case yielding url null, the required identity/IBAN information, and the owner/admin permission gate. It does not mention rate limits or failure modes, keeping it below a 5.

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 dense sentence with the action, return shape, and constraints front-loaded, and no wasted wording. It is compact but relies on semicolon-clauses that pack several distinct facts together.

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 mutation tool with no output schema, the description covers the essentials an agent needs: what it returns, the already-active case, permission requirements, and country default. The undocumented business parameters are the main remaining gap.

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 only 20% (just the force flag), so the description carries most of the burden. It adds real value by documenting that country is ISO-formatted with FR as default, but email, businessName, and businessType are left undocumented in both places, leaving a 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?

States a concrete verb and resource: activate the client's payment collection via Stripe Connect Express, and names the output (url, signup link, state). It is clearly distinguishable from get_payment_onboarding_status because it emphasizes activation rather than reading status, though it never names the sibling explicitly.

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?

Provides useful calling context: owner or administrator is required, and if collection is already active you get url null. However it never says when to choose this versus get_payment_onboarding_status or the other payment-page tools, so alternatives are left implicit.

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.