Skip to main content
Glama

Outil.io

Get poster

get_poster
Read-only

Lire une affiche enregistrée (document, version, derniers exports).

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": {
      "posterId": "<posterId>"
    },
    "name": "get_poster"
  }
}

Input Schema

NameRequiredDescriptionDefault
posterIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds useful context about what is returned (document, version, latest exports), but says nothing about error behavior for a missing poster or any access constraints.

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?

A single short sentence with the resource and return contents front-loaded; no filler. It is terse to the point of omitting usage context, but nothing is wasted.

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 carries the burden of describing returns and does so partially (document, version, latest exports). For a simple single-parameter getter this is close to adequate, but the French-only text and missing failure/ID semantics leave gaps.

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?

Only one parameter (posterId, uuid) with 0% schema description coverage, but its meaning is largely self-evident from the name and the tool's purpose. The description does not clarify whether the ID is a poster ID vs. a version or export ID, which is the one ambiguity worth resolving.

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?

States a specific verb ("Lire") and resource ("affiche enregistrée") and even hints at the payload (document, version, derniers exports). It is clearly a read of an existing poster, distinguishable from create_poster/update_poster/export_poster, though it never names those siblings.

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

Usage Guidelines2/5

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

No explicit when-to-use or when-not-to-use guidance. "enregistrée" implies the poster must already exist, but nothing tells the agent how this differs from list_poster_templates or export_poster, or what to do if the ID is unknown.

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.