Skip to main content
Glama
Sign In

Outil.io

by io.outil
OverviewDiscussionsAdmin

Configure payment page webhook

configure_payment_page_webhook
Destructive

Administrateur : définir la destination HTTPS du webhook envoyé après paiement confirmé ; URL vide pour désactiver. rotate true renouvelle la signature. Le secret n’est renvoyé qu’à sa création/rotation : le conserver hors conversation.

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

Input Schema

NameRequiredDescriptionDefault
idYes
urlYes
rotateNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, and the description adds real context on top: an empty URL disables the webhook, rotate=true renews the signature, and the secret is only returned at creation/rotation and must be stored outside the conversation. That last point is a valuable, non-obvious operational constraint. It stops short of saying what happens to an existing secret when the URL is overwritten.

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 clauses, front-loaded with the actor and the resource, then the disable semantics, then the rotation and secret handling. No filler. The telegraphic French phrasing is dense but each clause earns its place.

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 destructive, unannotated-at-the-field-level mutation with no output schema, the definition covers the important behavioral risks (disable-by-empty, secret exposure window). It remains incomplete on the identity and format of the required 'id' parameter and on what the call returns when rotate is false.

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 explains url (HTTPS destination, empty string disables) and rotate (renews signature) well, but the required 'id' parameter is never described at all - an agent gets no confirmation that it is the payment page identifier.

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 a specific verb and resource: set the HTTPS destination of the webhook fired after a confirmed payment, on a payment page. It is clearly distinguishable from get_payment_page_webhook and retry_payment_page_webhook, but it never names those siblings or states the boundary 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?

"Administrateur" signals a permission prerequisite and "URL vide pour désactiver" gives one concrete usage mode (disabling), which is genuinely useful. However, there is no guidance on when to prefer this over get_payment_page_webhook for inspection, or over rotate_form_webhook_secret-style siblings for other webhook types.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Outil.io toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources