Skip to main content
Glama

InProcess Cockpit

Version de démo

version_demo
Destructive

La version gardée pour les démonstrations : marquer la version actuelle, revenir à la version de démo (code et données d'essai), ou ne plus en avoir.

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>",
      "action": "<action>"
    },
    "name": "version_demo"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYes
cockpitYesIdentifiant du cockpit (mes_cockpits)

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; the description goes beyond them by naming what is affected — code and test data are replaced on revert. It still doesn't state whether the current version is overwritten irreversibly before reverting.

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 front-loaded sentence that defines the resource and then lists the three operations in enum order. Dense but every clause carries information.

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 two-parameter destructive mutation with no output schema, the description covers purpose, enum semantics, and the affected data. A note about irreversibility of 'revenir' over existing state would close the remaining gap.

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?

Schema coverage is 50%, with the 'action' enum bare of per-value documentation; the description supplies the meaning of all three enum values (marquer/revenir/oublier), which is meaningful value beyond the schema. The 'cockpit' parameter remains covered only by the schema.

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 concrete resource (the demo version) and enumerates the three operations: mark the current version, revert to the demo version, or drop it. It is specific enough to act on, though the distinction from the sibling 'revenir_version'/'versions' is not addressed.

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?

The three enumerated actions imply when each branch applies, and 'code et données d'essai' hints at what reverting restores. However, there is no explicit when-to-use guidance versus 'versions' or 'revenir_version', and no stated prerequisites.

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