Skip to main content
Glama

Outil.io

Generate catalog page

generate_catalog_page
Read-only

Page catalogue générée depuis les produits actifs (catégories, images, formules, options, mise en avant, boutons Commander / Demander un devis), à la charte. Renvoie publicUrl (page hébergée) et html (section autonome à passer à import_html_page pour l’intégrer au site).

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

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

A4.1/5.0
Behavior4/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 real value beyond that by disclosing both return artifacts (publicUrl hosted page and html section) and the intended hand-off to import_html_page. It leaves ambiguous whether the hosted page is published/live or draft and whether it persists, which is the main remaining behavioral gap.

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 what is generated and followed by what is returned. The parenthetical content list is long but each item conveys scope; no filler text.

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 output schema, the description correctly spends its second sentence explaining the return values, and it covers the 5-parameter surface at a high level despite low schema coverage. It is nearly complete for a generator tool; only per-parameter meaning and the persistence/publish state of the hosted page are missing.

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?

Schema description coverage is only 20%, so the description must carry most parameter meaning. It clarifies the content domain (active products, categories, the Commander / Demander un devis buttons tied to quoteUrl) and implies productIds acts as a filter, but title, intro and the selection semantics of productIds (ordering, defaults when empty) are never explained.

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?

States a specific verb (générer) and resource (page catalogue), names the source data (produits actifs) and the concrete content it assembles (catégories, images, formules, options, mise en avant, boutons). It also names the downstream sibling import_html_page, so an agent can tell it apart from page-creation/composition siblings.

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

Usage Guidelines4/5

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

Gives clear context for use — build a themed catalog page from active products — and explains the two output paths (hosted publicUrl vs. standalone html for import_html_page). It stops short of explicit exclusions, e.g. when to prefer compose_page or create_page over this generator, so it is strong context without routing rules.

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.