Skip to main content
Glama

InProcess Cockpit

Demandes de l'équipe

demandes_equipe
Read-only

Ce que l'équipe a demandé à l'assistant du cockpit et qu'il ne savait pas faire : de quoi proposer la prochaine évolution.

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

Input Schema

NameRequiredDescriptionDefault
cockpitYesIdentifiant du cockpit (mes_cockpits)

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

C2.7/5.0
Behavior2/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 behavioral bar is lower, yet the description adds nothing beyond framing: no indication of volume, ordering, whether requests are deduplicated, how old they are, or what an entry looks like. For a tool whose output drives a product decision, the absence of any shape or recency disclosure is a real gap.

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 dense sentence with no filler, front-loading the content before the purpose. It is slightly elliptical in French syntax but every clause carries information.

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 read-only single-parameter tool with annotations and full schema coverage, the definition covers what the data is and why it matters. It stops short of describing the returned items or how they should be consumed when proposing an evolution, which is the tool's stated reason for existing.

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?

With only one parameter at 100% schema description coverage ('Identifiant du cockpit (mes_cockpits)'), the schema already carries the semantics and the description correctly adds nothing redundant. Baseline 3 applies; no extra meaning about scope or defaults is offered.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the resource (what the team asked the cockpit assistant that it couldn't do) and its downstream purpose (feeding the next evolution), which distinguishes it from equipe_cockpit and equipe_organisation. But it never states the operation — no verb such as 'list' or 'retrieve' — leaving the agent to infer this is a read that returns stored requests.

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?

The phrase 'de quoi proposer la prochaine évolution' hints at a use case but is a rationale rather than guidance: no explicit when-to-call, no prerequisites, and no named alternative among the many siblings (equipe_cockpit, vue_ensemble, avant_publication) that might also inform a roadmap decision.

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