Skip to main content
Glama

InProcess Cockpit

Publier

publier
Destructive

Met le cockpit en ligne pour l'équipe, ou met à jour la version en ligne, avec les vérifications du Studio. Demande un avant_publication sur ce cockpit dans les 30 dernières minutes. Refusé avec la raison et la solution si l'offre ou une vérification ne le permet pas.

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>",
      "message": "<message>"
    },
    "name": "publier"
  }
}

Input Schema

NameRequiredDescriptionDefault
adresseNoAdresse à la première publication (celle proposée par défaut)
cockpitYesIdentifiant du cockpit (mes_cockpits)
messageYesCe qui change pour l'équipe, en une ou deux phrases (montré dans « Nouveautés »)
accepter_supplementNoLa personne accepte le supplément d'un cockpit en ligne au-delà de son offre
confirmer_effacementNoIdentifiants des données à effacer que la personne a acceptées (avant_publication)

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4/5.0
Behavior4/5

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

Annotations already flag a non-read-only, destructive operation, and the description adds genuinely new behavior: the 30-minute freshness gate on the prerequisite check, and that refusals return an explanation plus a fix (including offer/entitlement limits). It does not explain the destructive side (data erasure confirmation) that the annotations imply, which keeps it below 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tight sentences: action first, then prerequisite, then failure behavior. Nothing is repeated from the schema and no sentence is wasted.

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 five-parameter mutating tool with no output schema, the description covers the trigger, the gate, and the refusal response, which is what an agent needs to sequence the call after avant_publication. What happens on success (the resulting online state or version change) is left implicit.

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 coverage is 100%, so every parameter including adresse, message, accepter_supplement and confirmer_effacement is already documented. The description only gestures at the entitlement case ('si l'offre ... ne le permet pas') without adding format, ordering, or dependency detail beyond the schema.

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 gives a specific verb-and-resource pair: putting the cockpit online for the team, or updating the already-online version, with 'vérifications du Studio'. That is far more than a restatement of the name 'Publier', though it never explicitly names how it differs from siblings such as etat_en_ligne or versions.

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?

It states a concrete precondition (an avant_publication on this cockpit within the last 30 minutes) and the outcome when conditions are not met (refusal with reason and remedy). That tells the agent when the call is valid and what to do first, but no explicit alternative tool or 'do not use when' guidance is offered.

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