Skip to main content
Glama
assoujojo82-coder

synergieloc — French Real-Estate Legal Calculations

by assoujojo82-coder
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

fiche_mission

Generate a mission sheet for a craftsman preparing an intervention or worksite, capturing client, address, timeline, budget, and task progress.

Instructions

QUAND un artisan prépare une intervention ou un chantier. Fiche mission / chantier (app Missions). HTML ; PDF via POST /api/v1/documents/fiche-mission. Dossier local — pas d'accès au portail SaaS.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
lieuNoLieu d'établissement imprimé avant la date (« Fait à … »).
titreYesObjet de la mission, en une ligne.
budgetNoEnveloppe allouée, en euros.
etapesNoÉtapes de la mission, dans l'ordre, avec leur état d'avancement.
statutNoAvancement de la mission : à faire, en cours, terminée, annulée.
echeanceNoDate de fin attendue. Format ISO AAAA-MM-JJ. Par défaut, la date du jour.
referenceNoRéférence interne, pour rattacher la mission à un dossier.
client_nomNoClient donneur d'ordre.
descriptionNoDétail de ce qui est demandé : périmètre, contraintes, résultat attendu.
intervenantNoPersonne ou entreprise chargée de l'exécution.
date_emissionNoFormat ISO AAAA-MM-JJ. Par défaut, la date du jour.
client_adresseNoAdresse du destinataire. Sert au bloc fenêtre : il est poussé À DROITE pour une enveloppe à fenêtre.
entreprise_nomNoNom de l'entreprise émettrice, en en-tête du document.
adresse_chantierNoAdresse du lieu d'exécution.
entreprise_adresseNoAdresse de l'entreprise émettrice.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

A3.8/5.0
Behavior3/5

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

It discloses that it works with local files and does not access a SaaS portal, and mentions the output format and endpoint. However, it does not explicitly state whether the operation is read-only or has side effects, though generating a document is implicitly non-destructive.

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?

The description is concise, using a single sentence with the trigger condition upfront, making it easy 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?

Given the 15 parameters and lack of output schema, the description provides the essential context (when to use, output format, local vs SaaS), but does not elaborate on parameter handling. However, since the schema covers parameters, it is sufficiently complete.

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?

The schema already provides full descriptions for all 15 parameters (100% coverage). The tool description adds no extra parameter-specific meaning, so it does not improve on the baseline.

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 clearly states the purpose: it is for when a craftsman prepares an intervention or worksite, generating a mission sheet. It differentiates from siblings by the name and use case.

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 provides a condition (when a craftsman prepares an intervention) but does not explicitly contrast with alternative tools like 'bon_intervention' or mention when not to use it. Thus, partial guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools