Skip to main content
Glama
assoujojo82-coder

synergieloc — French Real-Estate Legal Calculations

by assoujojo82-coder
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

fiscal_synthese

Compare French rental income tax regimes (micro-foncier vs réel) to determine the better option, using gross receipts and deductible charges.

Instructions

QUAND un bailleur se demande s'il a intérêt au micro-foncier ou au réel — typiquement à l'approche de la déclaration. INDICATIF. Synthèse fiscale revenus fonciers (INDICATIVE) : compare micro-foncier (abattement 30 %, seuil 15 000 €) et régime réel (2044). À titre indicatif dans la limite des documents/données fournis — ni conseil fiscal ni déclaration ; renvoyer vers un professionnel. JSON via POST /api/v1/fiscal/synthese (format=json) ou PDF. Stateless — recettes_brutes + charges_deductibles.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
anneeNoAnnée fiscale concernée, sur quatre chiffres.
formatNoDéfaut json côté MCP (retour structuré)
agence_nomNoAgence qui établit la synthèse.
recettes_brutesYesLoyers encaissés sur l'année, charges récupérées comprises, en euros.
proprietaire_nomNoPropriétaire concerné par la synthèse.
charges_deductiblesYesCharges déductibles réellement payées sur l'année, en euros — travaux, intérêts, taxe foncière, assurance.
proprietaire_adresseNoAdresse du destinataire. Sert au bloc fenêtre : il est poussé À DROITE pour une enveloppe à fenêtre.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

A3.7/5.0
Behavior3/5

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

No annotations, so the description carries the burden. It discloses statelessness, output formats (JSON/PDF), and envelope address behavior, but does not clarify whether the tool persists documents, has side effects, or only returns a response.

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?

Description is compact and front-loaded with the use case, but contains redundancy (INDICATIF/À titre indicatif) and mixes technical endpoint details with tax context, slightly reducing conciseness.

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?

No output schema means the description should clarify the return value. It mentions JSON/PDF formats and 'synthèse', but not the actual JSON structure or what comparison data is included, leaving response expectations partly underspecified.

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?

Schema already covers 100% of parameters with detailed unit/scope descriptions. The description reinforces the key recettes_brutes + charges_deductibles inputs and adds relevant tax context (30% allowance, 15k threshold), improving semantic clarity beyond the schema.

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?

Description clearly defines when to use the tool (landlord comparing micro-foncier vs réel before tax filing) and its core function of comparing regimes. However, it doesn't explicitly state whether the primary output is a calculated comparison or a generated document, leaving slight ambiguity.

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?

Starts with 'QUAND' and gives a precise trigger scenario, plus exclusions (not tax advice or filing, refer to professional). It doesn't name sibling alternatives, but the when/not-when guidance is sufficient for tool selection.

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