Skip to main content
Glama
Sign In

Outil.io

by io.outil
OverviewDiscussionsAdmin

Update payment page

update_payment_page
Destructive

Remplacer la configuration complète avec la version actuelle. status archived ferme le lien public. Ne modifie ni le prix du produit ni les transactions existantes.

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>",
      "version": "<version>",
      "name": "<name>",
      "productId": "<productId>",
      "status": "<status>",
      "config": "<config>"
    },
    "name": "update_payment_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
nameYes
configYesConfiguration complète : lire describe_payment_pages pour les champs et valeurs par défaut.
statusYes
versionYes
productIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

Beyond the destructiveHint=true annotation, the description discloses two real behavioral facts: setting status to archived closes the public link, and the operation leaves product pricing and existing transactions untouched. What it does not disclose is the role of `version` (apparently an optimistic-concurrency guard) or what happens on a stale version.

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 replacement semantics and then the two behavioral caveats; no filler. Minor friction from being in French while the name, title, and sibling tools are English.

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, all-or-nothing replacement with a nested config object, a version field, and no output schema, the description covers the key side effects but omits the read-modify-write requirement and version-conflict behavior, which are the main ways an agent would call this incorrectly.

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?

With only 17% schema description coverage, the description partially compensates: it explains the effect of status=archived and that productId changes do not alter price. It says nothing about `version`, `id`, or `name`, leaving three of six required parameters explained only by type/pattern constraints.

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?

"Remplacer la configuration complète" states a specific verb (full replacement) and resource scope, and the second sentence clarifies a side effect of one field. It does not explicitly name the resource as a payment page nor differentiate from create_payment_page or describe_payment_pages in prose (the schema does that instead).

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

Usage Guidelines2/5

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

There is no explicit when-to-use / when-not-to-use guidance and no named alternative. The full-replacement wording hints that a partial patch is not possible and the schema points at describe_payment_pages for reading first, but the agent must infer that workflow.

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