Skip to main content
Glama

Outil.io

Get payment onboarding status

get_payment_onboarding_status
Read-only

État de l’encaissement : mode (connect, dedicated, none), chargesEnabled, payoutsEnabled, requirementsDue, testMode. À vérifier avant d’envoyer un devis avec acompte ou un lien de paiement.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds value beyond that by acting as a gating check before emitting payment artifacts and by disclosing the returned state fields, which matters because no output schema exists. Remaining gaps (cost, caching, whether the result is per-site or per-user) are minor.

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 with no filler: one enumerates the returned state, the second states the decision point. The field list is front-loaded and useful. Slightly terse for a non-French-reading consumer, but nothing is wasteful.

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?

With no output schema, the description properly compensates by listing the exact return fields and the enum values for mode, which is what an agent needs to interpret the result. What is missing is the follow-up path when the status is incomplete, so an agent must infer that start_payment_onboarding is the remedy.

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

Parameters4/5

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

The tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline of 4 applies. The description correctly implies a no-argument call by framing the tool as a status read with no inputs.

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 names the resource ("État de l'encaissement") and enumerates the concrete state fields returned: mode (connect, dedicated, none), chargesEnabled, payoutsEnabled, requirementsDue, testMode. An agent immediately knows this is a read of payment-onboarding readiness. It does not explicitly distinguish itself from sibling start_payment_onboarding or the payment-page getters, so it falls short of a 5.

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?

"À vérifier avant d'envoyer un devis avec acompte ou un lien de paiement" gives an explicit precondition/timing rule that an agent can act on. It stops short of naming alternatives or stating what to do when the status is not ready (e.g., invoking start_payment_onboarding), so no exclusions or sibling routing.

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.