Skip to main content
Glama

InProcess Cockpit

Mascotte de l'assistant

mascotte
Read-only

Où en est la mascotte de l'assistant du cockpit : toujours le caméléon InProcess, aux couleurs et à la tenue du métier, que la plateforme dessine d'elle-même après la première étape terminée. Montre si elle est posée, en cours de dessin, ou si l'assistant a encore le caméléon violet. Une autre version se dessine dans le Studio (Réglages › Mascotte).

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

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.6/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=true; the description adds genuine behavior the agent could not infer: the platform draws the mascot automatically after the first step completes, and the readable state space has three values (settled, being drawn, still the default purple chameleon). That is useful context beyond the annotation, though it does not describe the response shape or timing semantics of 'en cours de dessin'.

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

Conciseness3/5

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

The state question is front-loaded, but the prose is literary and padded ('toujours le caméléon InProcess, aux couleurs et à la tenue du métier, que la plateforme dessine d'elle-même...'). The three possible states are the core payload and are buried mid-paragraph rather than enumerated cleanly.

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 single-parameter, read-only status tool with no output schema, the description covers what matters: what the mascot is, the states it can be in, and that it is generated automatically. Return format is not spelled out, but the enumerated states largely substitute for it.

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?

There is a single parameter (cockpit) with 100% schema description coverage ('Identifiant du cockpit (mes_cockpits)'), so the schema already carries the meaning. The description never mentions the cockpit identifier or references mes_cockpits, adding no meaning beyond the schema; 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 the resource precisely (the cockpit assistant's mascot) and states what the tool reports: whether it is settled, being drawn, or still the purple chameleon. The verb is implicit ('Où en est...') rather than an explicit 'returns/reports', but an agent can still tell this is a read of mascot state and that it differs from the Studio-side version.

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 only implied: the text suggests checking the mascot's progress and notes that a different version lives in Studio settings (Réglages › Mascotte), which lightly routes the agent away from using this tool for configuration. There is no explicit when-to-use versus sibling tools, and the Studio pointer names a UI location rather than an alternative tool.

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