Skip to main content
Glama

InProcess Cockpit

Revenir à une version

revenir_version
Destructive

Remet l'aperçu du cockpit dans l'état d'une version (code, puis données d'essai remises à zéro). Ne touche pas au cockpit en ligne.

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": {
      "cockpit": "<cockpit>",
      "version": "<version>"
    },
    "name": "revenir_version"
  }
}

Input Schema

NameRequiredDescriptionDefault
cockpitYesIdentifiant du cockpit (mes_cockpits)
versionYesL'identifiant court d'une version (versions)

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and readOnlyHint=false, so the safety profile is partly covered. The description still earns credit for disclosing the *order and scope* of the destruction — code is restored first, then trial data is wiped — plus the blast-radius limit that the live cockpit is untouched. It stops short of saying whether the reset is reversible.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single compact sentence with the primary action front-loaded and the scoping caveat immediately after. Every clause carries information — the parenthetical even clarifies the ordering of the two destructive steps — with no filler.

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 destructive two-parameter tool with no output schema, the definition covers what changes, in what order, and what is left alone, which is most of what an agent needs. The main residual gap is reversibility — whether the previous preview state can be recovered after the reset.

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% and both parameters are documented in the schema with pointer hints to mes_cockpits and versions. The description adds no parameter-level meaning (e.g. format of the short version id, or behaviour if the id is stale), so the baseline of 3 applies.

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 gives a specific verb and scope: it resets the cockpit *preview* to the state of a version, and explicitly states it does not touch the live cockpit. That preview-vs-live distinction is genuinely useful, but it never names a sibling (e.g. version_demo, publier or versions) so the agent must infer routing from context alone.

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?

Usage is implied rather than stated: the 'ne touche pas au cockpit en ligne' clause tells the agent this is the non-production path, but there is no explicit when-to-use, no prerequisite (e.g. must the cockpit be unpublished?), and no named alternative. An agent can guess, but it is not routed.

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