Skip to main content
Glama

InProcess Cockpit

Lien de la démo

lien_demo
Read-only

Le lien de l'aperçu du cockpit à donner à la personne (valable 7 jours, avec ses comptes d'essai), et celui du cockpit dans le Studio.

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": "lien_demo"
  }
}

Input Schema

NameRequiredDescriptionDefault
cockpitYesIdentifiant du cockpit (mes_cockpits)

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.7/5.0
Behavior4/5

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

readOnlyHint=true already establishes this is a safe read, and the description adds meaningful behavioral context: the preview link is valid for 7 days and includes trial accounts. That expiration and content disclosure goes beyond what annotations provide, though it doesn't mention authorization requirements or the exact shape of the returned pair of links.

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?

The definition is a single front-loaded sentence with no filler. It could be marginally clearer with an explicit verb, but every clause (preview link, 7-day validity, trial accounts, Studio link) 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 one-parameter read-only tool with no output schema, the description covers the key return values (preview link and Studio link) and the important 7-day validity constraint. It is nearly complete; only the exact response structure and any permission requirements are left implicit.

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% for the single 'cockpit' parameter, so the schema already documents that it expects a cockpit identifier from mes_cockpits. The description only refers to 'du cockpit' without adding format or lookup details, so the baseline of 3 is appropriate.

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 identifies the specific resource: the cockpit preview link and the Studio link. It doesn't use an explicit verb like 'retrieve' or 'return', but the noun phrase clearly signals what the tool produces and distinguishes it from lien_paiement by naming the demo preview and Studio contexts.

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 phrase 'à donner à la personne' implies the usage context of sharing a link with someone, but there is no explicit when-to-use guidance, no exclusions, and no reference to alternatives such as lien_paiement or version_demo. The implied context is enough to orient an agent but leaves selection between sibling tools to inference.

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