Skip to main content
Glama

InProcess Cockpit

Méthode de construction

guide
Read-only

La méthode et les règles de construction d'un cockpit InProcess, telles que l'agent du Studio les suit, avec la liste des skills et ce que la plateforme sait faire. Utile avant de créer ou de faire évoluer un cockpit.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "guide"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.8/5.0
Behavior3/5

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

readOnlyHint=true already tells the agent this is a safe, non-mutating read, so the description does not need to restate that. It adds that the payload contains the rules the Studio agent follows, the skill list, and platform capabilities, which is useful content disclosure. It says nothing about length, format, or how to interpret the returned material once fetched, leaving a modest 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?

Two compact sentences, front-loaded with what the tool returns and closing with when to call it. No filler or redundancy, though the enumeration of contents (rules, skills, capabilities) is slightly loose rather than crisply structured.

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 zero-parameter, read-only reference tool with no output schema, the description covers what the agent gets back and when to reach for it. An agent could call this correctly with no further information; only the shape and size of the returned guidance remain unstated.

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?

The tool takes zero parameters, so there is no parameter semantics to explain and the baseline of 4 applies. The description correctly does not invent arguments or filters that do not exist.

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 concretely: the construction method and rules of an InProcess cockpit, plus the list of skills and platform capabilities. That is a specific verb-less but clearly scoped retrieval, and it is distinguishable from siblings like 'lire_skill' (individual skill) or 'nouveau_cockpit' (creation) by framing itself as the overall method reference. It stops short of naming a sibling explicitly, so it lands at 4 rather than 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The closing sentence 'Utile avant de créer ou de faire évoluer un cockpit' gives a clear when-to-use condition tied to concrete actions. It does not state when not to use it or route to a named alternative, but the timing guidance is unambiguous.

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