Skip to main content
Glama
assoujojo82-coder

synergieloc — French Real-Estate Legal Calculations

by assoujojo82-coder
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

compte_rendu_chantier

Generate construction site progress reports with details on completed tasks, risks, and next steps for client communication.

Instructions

QUAND il faut rendre compte de l'avancement d'un chantier au client. Compte-rendu d'avancement (app Chantier IA). POST /api/v1/documents/compte-rendu-chantier. points[] = {libelle, statut, notes}.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titreYesObjet du compte rendu — « Visite hebdomadaire, lot gros œuvre ».
pointsNoPoints traités pendant la visite, avec leur suite à donner.
risquesNoRisques et réserves relevés, qui engagent la responsabilité s'ils ne sont pas signalés.
client_nomNoMaître d'ouvrage destinataire du compte rendu.
date_visiteNoDate de la visite. Format ISO AAAA-MM-JJ. Par défaut, la date du jour.
date_emissionNoFormat ISO AAAA-MM-JJ. Par défaut, la date du jour.
entreprise_nomNoNom de l'entreprise émettrice, en en-tête du document.
pct_avancementNoAvancement constaté, en pourcentage de 0 à 100.
prochaine_etapeNoProchaine échéance du chantier et ce qu'elle attend.
adresse_chantierNoAdresse du chantier visité.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

A3.9/5.0
Behavior2/5

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

No annotations are present, so the description carries the full behavioral burden. It reveals a POST endpoint and the recipient ('au client'), which implies a document-creation side effect, but it never states what happens after invocation (whether a document is stored, sent, or returned) nor any auth/permission requirements. That is a significant gap for a mutating tool.

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 compact: a usage trigger, a human-readable name, an endpoint, and the key payload shape, with no filler. The when-condition is front-loaded, making it easy for an agent to scan.

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?

For a 10-parameter, no-annotation, no-output-schema mutation tool, the description covers when and how to call it, and the schema covers the parameters. However, it omits the result of the call, side effects, and any prerequisites, so it is not fully self-sufficient.

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 schema already describes all 10 parameters, so the baseline is 3. The description adds genuine value by specifying the internal structure of points[] as {libelle, statut, notes}, which the schema leaves open, and by giving an example tone for titre. This pushes it above 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 immediately states what the tool is for: reporting construction-site progress to the client, and identifies the concrete artifact ('Compte-rendu d'avancement') and endpoint. No sibling tool covers this same document, so the purpose is unambiguous.

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?

It begins with 'QUAND...' providing a clear trigger condition (when a site progress report to the client is needed). It does not mention when not to use it or name alternatives, so it stops at clear context rather than full routing 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