Skip to main content
Glama

InProcess Cockpit

Avant de publier

avant_publication
Read-only

Tout ce qui compte avant de publier, sans rien publier : l'offre (essai, place en ligne, supplément), l'adresse, les vérifications du cockpit, et les données qui seraient effacées. Quelques minutes au plus.

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

Input Schema

NameRequiredDescriptionDefault
adresseNoAdresse voulue à la première publication (ex. plomberie-martin)
cockpitYesIdentifiant du cockpit (mes_cockpits)

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, and the description reinforces rather than contradicts this with 'sans rien publier'. It adds real behavioral value beyond the annotation by disclosing the scope of the checks and, notably, that the result surfaces 'les données qui seraient effacées' plus a duration expectation ('quelques minutes au plus'). It does not describe the response shape, but no output schema exists to fall back on.

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?

The scope statement is front-loaded in a single dense sentence, and the closing 'quelques minutes au plus' efficiently sets an effort expectation. The parenthetical enumeration is slightly compressed but every clause carries distinct information.

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 read-only, two-parameter tool with no output schema, the description covers what is inspected (offer, address, cockpit checks) and what the agent learns (data that would be erased), which is enough to call it correctly. Only the returned structure remains unspecified, which is a minor gap given the absence of an output schema.

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%, so both parameters (cockpit, adresse) are already documented in the schema. The description echoes the address and cockpit checks but adds no syntax, format, or constraint details beyond what the schema provides, which is the expected baseline.

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 a distinct resource scope — the offer (trial, online slot, supplement), the address, cockpit checks, and data that would be erased — which an agent can clearly tell apart from the sibling 'publier'. The operation itself (a dry-run/audit returning information) is implied by 'sans rien publier' rather than stated with a specific verb, so it falls just short of a 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?

'Tout ce qui compte avant de publier, sans rien publier' establishes the timing (before publishing) and the exclusion (this tool performs no publication), implicitly routing actual publication to 'publier'. It gives no further conditions or prerequisites, but the context 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