Skip to main content
Glama

InProcess Cockpit

Versions du cockpit

versions
Read-only

Les versions du cockpit (la plus récente en premier), la version de démo marquée, et ce qui est publié.

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

Input Schema

NameRequiredDescriptionDefault
cockpitYesIdentifiant du cockpit (mes_cockpits)

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

B3.2/5.0
Behavior3/5

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

readOnlyHint=true already tells the agent this is a safe read, so the description's job is only to add return-value context — and it does, disclosing the sort order (most recent first), that the demo version is marked, and that publication state is included. With no output schema, however, a fuller account of the returned fields (identifiers, dates, counts) would have been warranted.

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 compact sentence with the resource and the ordering/flag details front-loaded; nothing is wasted. It is a fragment rather than a sentence, which costs a point on structure but not on clarity.

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 one-parameter read tool with no output schema, the description covers ordering and the notable flags, which is adequate but leaves the returned version fields and how to act on a version (revenir_version) unspecified. It never mentions the link back to mes_cockpits beyond what the schema already says.

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%: the single required cockpit parameter is documented as an identifier from mes_cockpits. The description adds nothing about that parameter, so the baseline 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 names a specific resource (the cockpit's versions) and states the shape of what is returned: most recent first, the demo version flagged, and what is published. It is a noun-phrase fragment with no verb (list/read), which is why it falls short of 5; it also does not distinguish itself from the sibling revenir_version, which acts on the same objects.

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 statement of when to call this versus other versions-related tools such as revenir_version or version_demo, and no preconditions or exclusions. The agent must infer usage from the name alone.

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