Skip to main content
Glama

Outil.io

Create poster

create_poster

Composer une affiche ou un visuel commercial et l’enregistrer dans le projet : modèle + format + textes + photos (url, assetId ou recherche Pexels) + QR code vers une page ou un tunnel. Couleurs, polices, logo et coordonnées viennent de la charte. Renvoie l’id, la version, des remarques (texte trop long, image ignorée) et un APERÇU à contrôler visuellement.

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": {
      "templateId": "<templateId>",
      "format": "<format>"
    },
    "name": "create_poster"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
qrUrlNoLien encodé dans le QR code (page, tunnel, prise de RDV)
textsNo
colorsNoSurcharge ponctuelle de la charte
formatYes
imagesNo1re = photo principale ; plaquette : 2e et 3e à l’intérieur
landscapeNoAffiche/flyer à l’italienne
templateIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly=false, destructive=false and openWorld=true, and the description adds real context on top: styling is inherited from the brand charter (couleurs, polices, logo, coordonnées), Pexels is queried for free photos, and the response carries id, version, warnings (texte trop long, image ignorée) and a preview that must be visually checked. The mention of a preview to verify is a genuine behavioral nuance an agent would not get from annotations.

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 dense sentence that front-loads the action and the payload before the brand-charter inheritance and the return shape. No filler; each clause carries information, though the lack of sentence breaks makes it slightly harder to scan.

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 an 8-parameter tool with nested objects and no output schema, the description covers both the input composition model and the return contract (id, version, remarks, preview). Remaining gaps are minor: no guidance on choosing among the six templateId values or on how the charter is resolved.

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

Parameters4/5

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

Schema coverage is only 50%, and the description compensates by naming the payload groups: modèle + format + textes + photos (url, assetId ou recherche Pexels) + QR code vers une page ou un tunnel. That maps directly onto the templateId/format/texts/images/qrUrl fields and clarifies the three accepted image input forms, which the schema alone states only via anyOf.

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 opens with a specific verb and resource ('Composer une affiche ou un visuel commercial') and adds that it persists into the project, which separates it from read/export siblings by name alone. It never explicitly contrasts itself with update_poster or export_poster, so differentiation is implied rather than stated.

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 makes clear this is the creation step for a poster ('et l'enregistrer dans le projet'), so an agent can infer it is the entry point rather than a modification. There is no guidance on prerequisites (e.g., discovering templateId via list_poster_templates) or on when to prefer it over create_presentation or update_poster.

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.