Skip to main content
Glama

Outil.io

Export poster

export_poster

Exporter une affiche : PNG au format fini (300 dpi en impression, 100 dpi pour le kakémono, taille native pour les réseaux) et PDF imprimable avec 3 mm de fonds perdus (couleurs RVB, l’imprimeur convertit en CMJN). Recto/verso ou extérieur/intérieur en 2 pages. Les fichiers sont ajoutés aux médias du projet.

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

Input Schema

NameRequiredDescriptionDefault
formatsNo
versionNo
posterIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false and openWorldHint=true; the description adds genuinely new behavioral context by stating the files are written into the project's media library and by disclosing the color-space caveat (RGB output, printer converts to CMYK) and the bleed assumption. It does not say whether re-exporting overwrites prior files or what identifiers come back, but the side-effect disclosure is the key value-add here.

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 sentences, front-loaded with the output formats and free of filler; every clause (bleed, color space, page count, destination folder) carries information. It is dense rather than padded, though a slightly more structured layout for the per-medium resolutions would scan faster.

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?

For a 3-parameter tool with no output schema, the description covers the product side (formats, resolutions, bleed, recto/verso) well. It leaves gaps on the input side ("version" unexplained) and does not indicate what an agent receives back after the export beyond "files are added to project media", which matters for chaining calls.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across all three parameters, so the description carries the full burden. It does explain what png versus pdf yield (bleed, RGB/CMYK conversion) and thus informs the "formats" array choice, but the "version" integer parameter is never mentioned and "posterId" is not characterized, leaving the caller to guess two of three parameters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb+resource ("Exporter une affiche") and immediately specifies the two artifact types produced (PNG at use-case-specific resolutions, printable PDF with 3 mm bleed). Combined with the tool name and the sibling set (export_catalog_pdf, export_presentation), an agent can tell this is the poster-specific export without opening the schema.

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?

There is no explicit when-to-use / when-not-to-use statement and no named alternative, so routing guidance is only implied by the tool name. The resolution presets (300 dpi print, 100 dpi kakemono, native size for social) do implicitly signal which output to pick for which medium, which is more than nothing but falls short of explicit guidance.

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.