Skip to main content
Glama

Outil.io

List poster templates

list_poster_templates
Read-only

Modèles d’affiches maison et formats (A4, A3, flyer A5, carte de visite, post carré, story, bannière web, kakémono, plaquette 2 volets) avec les textes attendus. Mise en page déterministe remplie avec la charte, sans IA générative.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_poster_templates"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/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 genuinely non-structured context: layouts are deterministic and filled with the brand charter, with no generative AI — useful for predicting output stability. It says nothing about result size, ordering, or how templates relate to poster creation.

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 resource and then lists formats in a parenthetical. Every clause carries information, though the long format enumeration is somewhat heavy for a description when the same detail will appear in the results.

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?

With no parameters, no output schema and read-only annotations, the burden is light, and the description does explain what the returned entries contain (formats plus expected texts) and how layout is produced. It could still mention the practical next step (feeding a template into create_poster) to be fully complete.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The enumerated format names in the description do inform the agent about the value space of returned template entries, which is a mild bonus.

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 the resource (in-house poster templates) and enumerates the concrete formats returned (A4, A3, A5 flyer, business card, square post, story, web banner, kakemono, 2-panel brochure) plus the expected texts, which is specific enough to distinguish it from list_posters (created posters) rather than templates. It never states the verb explicitly (listing/retrieving), relying on the tool name, so it stops just short of a 5.

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?

There is no statement of when to call this tool versus alternatives such as list_posters or the other list_*_templates siblings, and no prerequisite or sequencing guidance (e.g. 'use before create_poster to pick a template'). Usage must be inferred entirely from the tool name.

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.