Skip to main content
Glama

InProcess Cockpit

Logo du cockpit

logo
Destructive

Pose le logo du cockpit (et ses icônes) à partir d'une image PNG publique, téléchargée à l'adresse https donnée (le logo du site de l'entreprise, par exemple), ou le retire. L'adresse est celle d'un fichier image, pas d'une API.

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

Input Schema

NameRequiredDescriptionDefault
urlNoAdresse https d'une image PNG, 2 Mo au plus
cockpitYesIdentifiant du cockpit (mes_cockpits)
retirerNo

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false and destructiveHint=true; the description earns credit for saying what is actually affected (the logo and its icons are replaced, or removed) and that content is fetched from an external public https URL. It omits permissions, failure behavior, and whether the change is immediately visible on a published cockpit.

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 the action and followed by the input constraint, with no filler. The parenthetical example is short and useful rather than padding.

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 and a destructive mutation, an agent would still benefit from knowing what a successful call returns, whether removal is reversible, and what happens on fetch failure or oversized files. The description covers the core action and input shape but stops short of that operational context.

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 67%, so the schema documents most fields, but 'retirer' is undocumented there and the description only maps it implicitly via 'ou le retire'. It adds a genuine nuance for 'url' (must be an image file, not an API endpoint) but does not explain the interaction between 'url' and 'retirer' or what 'cockpit' identifiers look like.

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 specific verb pair (pose / retire) and a specific resource (the cockpit logo and its icons) sourced from a public PNG image. It is unmistakably distinct from siblings like 'mascotte' or 'reglages', though it never explicitly contrasts itself with any named alternative.

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?

It gives real input-selection guidance ('the address is an image file, not an API', with a company-site logo example) and states the two modes of use (set or remove). However, it never says when to prefer this tool over related cockpit-configuration tools, so tool choice is left to inference.

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