Skip to main content
Glama

Outil.io

Export catalog PDF

export_catalog_pdf
Read-only

Brochure PDF du catalogue (couverture à la charte, produits par catégorie, prix, formules). Renvoie pdfUrl, lien public à partager.

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

Input Schema

NameRequiredDescriptionDefault
introNo
titleNo
categoryNo
quoteUrlNoLien du bouton « Demander un devis » (page formulaire, mailto:, tel:) ; e-mail de la charte par défaut
productIdsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3/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 bar is lower. The description adds useful behavior beyond them by disclosing the return value (pdfUrl) and, importantly, that the result is a PUBLIC share link — meaningful because openWorldHint=false might otherwise suggest no external exposure. It does not say whether a new file is created each call, whether previous exports persist, size limits, or permissions needed to publish a public link.

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 dense sentences, front-loaded with the artifact description and followed by the return value. No filler, though the parenthetical content list could be slightly reordered so the return value is not the only behavioral note.

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 correctly names pdfUrl, but for a 5-parameter tool with all parameters optional and 20% schema coverage it leaves too much open: default behavior with no arguments, how category filters products, and whether the link is permanent. Adequate but clearly incomplete for the tool's complexity.

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 only 20% — only quoteUrl is documented — so the description must carry the load for title, intro, category and productIds. It hints at category-based grouping ('produits par catégorie') but never explains what omitting productIds or category does (all products? empty PDF?), nor the role of title/intro. Most parameter meaning remains undocumented.

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?

Names a specific artifact: a catalog brochure PDF with brand cover, products grouped by category, prices and formulas. An agent immediately knows this produces a styled PDF rather than rows or a web page, though it never explicitly distinguishes itself from siblings like generate_catalog_page or export_collection_rows.

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 guidance on when to choose this over generate_catalog_page or the other export tools, no prerequisites, and no exclusions. The usage is only implied by the tool name and the mention of a shareable brochure.

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.