Skip to main content
Glama

InProcess Cockpit

Nouveau cockpit

nouveau_cockpit

Crée un cockpit vide (le noyau, AGENTS.md, les skills) dans l'organisation de la personne, prêt à être construit avec les outils de fichiers.

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": {
      "nom": "<nom>",
      "description": "<description>"
    },
    "name": "nouveau_cockpit"
  }
}

Input Schema

NameRequiredDescriptionDefault
nomYesNom du cockpit, en général celui de l'entreprise
descriptionYesLe métier et ce que le cockpit doit faire, tel que la personne l'a décrit

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the write-but-not-destructive profile is covered. The description adds real value by specifying the scaffold contents (core, AGENTS.md, skills) and the target scope (the person's own organization). It omits whether repeated calls create duplicates, what permissions are required, and what identifier or reference is returned.

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 sentence with zero filler, front-loading the action and then the resulting artifact. Nothing is repeated, though it is short enough that a little more routing detail could have been added without bloat.

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?

With only two mandatory, fully documented parameters and annotations covering the safety profile, the definition is close to sufficient. The notable gap is the absence of any statement about the return value (cockpit id, link, or nothing) for a creation tool that has no output schema, which leaves the agent unsure how to chain into the file tools.

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%, and the schema already explains that 'nom' is the cockpit/company name and 'description' is the métier the cockpit should serve. The description adds no format, length, or validation meaning beyond that, 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?

States a specific verb and resource ("Crée un cockpit vide") and enumerates what the artifact contains (noyau, AGENTS.md, skills) and where it lands (the person's organization). It stops short of differentiating itself from siblings like mes_cockpits or equipe_cockpit, so an agent must infer that this is the creation entry point.

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 trailing clause "prêt à être construit avec les outils de fichiers" implies the successor step (file tools) after creation, which is useful context. There is no explicit when-to-use vs when-not guidance, no prerequisites, and no mention of what to do if a cockpit already exists.

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