Skip to main content
Glama

Décrire un modèle

get_template
Read-onlyIdempotent

Décrit un modèle : champs à remplir (nom technique, libellé, obligatoire ou non, format attendu, options, valeur par défaut), champs calculés automatiquement et signataires. À appeler avant generate_document pour savoir quelles informations demander à l'utilisateur (ne les inventez pas) ; pour trouver le slug, utilisez list_templates. Lecture seule : ne crée rien.

Input Schema

NameRequiredDescriptionDefault
templateYesSlug du modèle renvoyé par list_templates, par exemple bail-meuble ou quittance-de-loyer.

Output Schema

NameRequiredDescriptionDefault
nameYesNom du modèle.
slugYesIdentifiant du modèle.
notesYesRègles à connaître avant de générer.
pagesNoNombre de pages du PDF.
signersYesSignataires du document.
categoryYesFamille de documents.
sectionsYesParties du formulaire, dans l'ordre du document.
guide_urlYesGuide du document sur remplirpdf.fr.
document_titleYesTitre imprimé sur le document.
computed_automaticallyYesChamps calculés par RemplirPDF : ne pas les fournir.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / template / enum
      Previous value: -[
      -  "etat-des-lieux",
      -  "etat-des-lieux-sortie",
      -  "quittance-de-loyer",
      -  "bail-meuble",
      -  "bail-location-vide",
      -  "bail-mobilite",
      -  "bail-etudiant",
      -  "bail-colocation",
      -  "bail-commercial",
      -  "bail-precaire",
      -  "etat-des-lieux-entree",
      -  "attestation-de-loyer",
      -  "avis-echeance-loyer",
      -  "attestation-hebergement",
      -  "attestation-hebergement-titre-gratuit",
      -  "acte-caution-solidaire",
      -  "preavis-logement",
      -  "conge-pour-vente",
      -  "attestation-fin-de-bail",
      -  "echeancier-paiement-loyer",
      -  "lettre-resiliation-bail-precaire",
      -  "solde-de-tout-compte-location"
      -]New value: +[
      +  "etat-des-lieux",
      +  "etat-des-lieux-sortie",
      +  "quittance-de-loyer",
      +  "bail-meuble",
      +  "bail-location-vide",
      +  "bail-mobilite",
      +  "bail-etudiant",
      +  "bail-colocation",
      +  "bail-commercial",
      +  "bail-precaire",
      +  "etat-des-lieux-entree",
      +  "attestation-de-loyer",
      +  "avis-echeance-loyer",
      +  "attestation-hebergement",
      +  "attestation-hebergement-titre-gratuit",
      +  "acte-caution-solidaire",
      +  "preavis-logement",
      +  "conge-pour-vente",
      +  "attestation-fin-de-bail",
      +  "echeancier-paiement-loyer",
      +  "lettre-resiliation-bail-precaire",
      +  "solde-de-tout-compte-location",
      +  "declaration-mise-en-location"
      +]
  2. Changed1 schema field changed
    • changedInput schema / properties / template / enum
      Previous value: -[
      -  "etat-des-lieux",
      -  "etat-des-lieux-sortie",
      -  "quittance-de-loyer",
      -  "bail-meuble",
      -  "bail-location-vide",
      -  "bail-mobilite",
      -  "bail-etudiant",
      -  "bail-colocation",
      -  "bail-commercial",
      -  "bail-precaire",
      -  "etat-des-lieux-entree",
      -  "attestation-de-loyer",
      -  "avis-echeance-loyer",
      -  "attestation-hebergement",
      -  "attestation-hebergement-titre-gratuit",
      -  "acte-caution-solidaire",
      -  "preavis-logement",
      -  "conge-pour-vente",
      -  "attestation-fin-de-bail",
      -  "echeancier-paiement-loyer",
      -  "lettre-resiliation-bail-precaire"
      -]New value: +[
      +  "etat-des-lieux",
      +  "etat-des-lieux-sortie",
      +  "quittance-de-loyer",
      +  "bail-meuble",
      +  "bail-location-vide",
      +  "bail-mobilite",
      +  "bail-etudiant",
      +  "bail-colocation",
      +  "bail-commercial",
      +  "bail-precaire",
      +  "etat-des-lieux-entree",
      +  "attestation-de-loyer",
      +  "avis-echeance-loyer",
      +  "attestation-hebergement",
      +  "attestation-hebergement-titre-gratuit",
      +  "acte-caution-solidaire",
      +  "preavis-logement",
      +  "conge-pour-vente",
      +  "attestation-fin-de-bail",
      +  "echeancier-paiement-loyer",
      +  "lettre-resiliation-bail-precaire",
      +  "solde-de-tout-compte-location"
      +]
  3. Changed1 schema field changed
    • changedInput schema / properties / template / enum
      Previous value: -[
      -  "etat-des-lieux",
      -  "etat-des-lieux-sortie",
      -  "quittance-de-loyer",
      -  "bail-meuble",
      -  "bail-location-vide",
      -  "bail-mobilite",
      -  "bail-etudiant",
      -  "bail-colocation",
      -  "bail-commercial",
      -  "bail-precaire",
      -  "etat-des-lieux-entree",
      -  "attestation-de-loyer",
      -  "avis-echeance-loyer",
      -  "attestation-hebergement",
      -  "attestation-hebergement-titre-gratuit",
      -  "acte-caution-solidaire",
      -  "preavis-logement",
      -  "conge-pour-vente",
      -  "attestation-fin-de-bail",
      -  "echeancier-paiement-loyer"
      -]New value: +[
      +  "etat-des-lieux",
      +  "etat-des-lieux-sortie",
      +  "quittance-de-loyer",
      +  "bail-meuble",
      +  "bail-location-vide",
      +  "bail-mobilite",
      +  "bail-etudiant",
      +  "bail-colocation",
      +  "bail-commercial",
      +  "bail-precaire",
      +  "etat-des-lieux-entree",
      +  "attestation-de-loyer",
      +  "avis-echeance-loyer",
      +  "attestation-hebergement",
      +  "attestation-hebergement-titre-gratuit",
      +  "acte-caution-solidaire",
      +  "preavis-logement",
      +  "conge-pour-vente",
      +  "attestation-fin-de-bail",
      +  "echeancier-paiement-loyer",
      +  "lettre-resiliation-bail-precaire"
      +]
  4. Changed1 schema field changed
    • changedInput schema / properties / template / enum
      Previous value: -[
      -  "etat-des-lieux",
      -  "etat-des-lieux-sortie",
      -  "quittance-de-loyer",
      -  "bail-meuble",
      -  "bail-location-vide",
      -  "bail-mobilite",
      -  "bail-etudiant",
      -  "bail-colocation",
      -  "bail-commercial",
      -  "bail-precaire",
      -  "etat-des-lieux-entree",
      -  "attestation-de-loyer",
      -  "avis-echeance-loyer",
      -  "attestation-hebergement",
      -  "attestation-hebergement-titre-gratuit",
      -  "acte-caution-solidaire",
      -  "preavis-logement",
      -  "conge-pour-vente",
      -  "attestation-fin-de-bail"
      -]New value: +[
      +  "etat-des-lieux",
      +  "etat-des-lieux-sortie",
      +  "quittance-de-loyer",
      +  "bail-meuble",
      +  "bail-location-vide",
      +  "bail-mobilite",
      +  "bail-etudiant",
      +  "bail-colocation",
      +  "bail-commercial",
      +  "bail-precaire",
      +  "etat-des-lieux-entree",
      +  "attestation-de-loyer",
      +  "avis-echeance-loyer",
      +  "attestation-hebergement",
      +  "attestation-hebergement-titre-gratuit",
      +  "acte-caution-solidaire",
      +  "preavis-logement",
      +  "conge-pour-vente",
      +  "attestation-fin-de-bail",
      +  "echeancier-paiement-loyer"
      +]
  5. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description reinforces this ("Lecture seule : ne crée rien") and adds genuinely new behavioral guidance — that it is a discovery/prerequisite step and that values must not be fabricated. Minor redundancy with the read-only annotation keeps it from a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with the resource description, then the workflow constraint. Every clause carries information — no filler, no repetition of the tool title.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return-value shape need not be explained, and annotations cover safety. The description supplies what structured fields cannot: the tool's role as a pre-generation discovery step and the prohibition on inventing field values. Nothing an agent needs to invoke it correctly is 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?

With a single required enum parameter at 100% schema coverage, the schema already documents the slug and its allowed values in detail. The description's note that the slug comes from list_templates largely restates the schema's own wording. Baseline 3 is appropriate here.

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 and resource ("Décrit un modèle") and then enumerates exactly what is returned: fields to fill with their attributes (technical name, label, required, format, options, default), auto-computed fields, and signatories. This distinguishes it clearly from list_templates (which only yields slugs) and generate_document (which consumes the values).

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

Usage Guidelines5/5

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

It gives an explicit ordering rule: call this before generate_document so the agent knows which information to request from the user, plus an explicit anti-pattern ("ne les inventez pas"). It also names the sibling to use for the prerequisite step (list_templates for the slug), so both the when and the alternative are spelled out.

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.