Skip to main content
Glama

InProcess Cockpit

Réglages du cockpit

reglages

Lit ou change le nom du cockpit, sa couleur, le nom sous l'icône, le nom de l'assistant et le tutoiement. Sans paramètre : les réglages actuels et les rôles.

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

Input Schema

NameRequiredDescriptionDefault
nomNo
cockpitYesIdentifiant du cockpit (mes_cockpits)
couleurNoCouleur principale, #rrggbb
nom_courtNoNom sous l'icône de l'application, 20 caractères au plus
tutoiementNoL'assistant tutoie l'équipe (vouvoiement par défaut)
nom_assistantNo

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.5/5.0
Behavior3/5

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

Annotations declare a non-destructive write (readOnlyHint=false, destructiveHint=false); the description usefully adds that omitting parameters turns the call into a read returning current settings plus roles. It does not state partial-update semantics (what happens to fields not supplied), who is allowed to change cockpit settings, or whether changes are immediate/reversible.

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?

Two sentences, no filler, with the capability list first and the no-parameter read behavior second. The field enumeration is long but each item earns its place by mapping to a distinct mutable setting.

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 no output schema, the description covers the read case (current settings and roles) but says nothing about what a successful change returns or confirms. For a settings-mutation tool it also leaves authorization and partial-update behavior unstated, which is a meaningful gap given the mixed read/write nature.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 67%, and the description compensates by naming all five optional fields in business terms ("le nom sous l'icône" for nom_court, "le nom de l'assistant" for nom_assistant, which has no schema description). Only the required cockpit identifier and the partial-update mechanics are left to the schema, so the description adds real meaning.

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?

"Lit ou change" gives a concrete verb pair and the resource is pinned down by enumerating the five mutable fields (nom, couleur, nom sous l'icône, nom de l'assistant, tutoiement). An agent knows exactly what surface this tool touches. It stops short of 5 because it does not differentiate itself from adjacent tools such as logo, mascotte or mes_cockpits, which an agent might confuse with visual/naming settings.

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?

"Sans paramètre : les réglages actuels et les rôles" gives a usable read-vs-write rule keyed on the presence of parameters, which is genuine when-to-use guidance. There is no when-not-to-use statement, no named alternative for listing cockpits (mes_cockpits appears only inside the schema), and no prerequisite/permission context.

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