hel

Devis public (tous niveaux)

hel-devis-public

Read-only

Donne le PRIX (coût, tarif, « combien coûte ») d'un service HEL : tarif public et tarifs réduits par niveau d'abonnement (Public, Essentiel, Privilège, Intégral). Lecture seule, sans authentification, sans donnée personnelle. Pour l'état hypothécaire (ehf), le prix total = un honoraire forfaitaire par niveau + des débours refacturés (12€/élément, 7€ en Alsace-Moselle pour Privilège/Intégral) calculés selon type_recherche et le nombre d'éléments. Fournis type_recherche et les nombres (nb_parcelles / nb_lots / nb_personnes) pour un devis EHF exact ; sans eux, seul l'honoraire forfaitaire est estimé (débours non calculés). Plafonds : 12 parcelles, 12 lots, 3 personnes.

Input Schema

TableJSON Schema

Name	Required	Description
`nb_lots`	No	EHF en copropriété : nombre de lots (max 12).
`service`	Yes	Service HEL : ehf, acte, rcp, edd, verif_mandat, pre_etat_date, pack_propriete, pack_rcp, pack_edd, rdv_analyste, analyse_ia, situation_patrimoine, recherche_proprietaire.
`copropriete`	No	EHF : true si le bien est en copropriété (on dénombre les lots au lieu des parcelles).
`nb_parcelles`	No	EHF, recherche cadastrale/combinee : nombre de parcelles (max 12).
`nb_personnes`	No	EHF, recherche identite/combinee : nombre de personnes physiques + morales (max 3).
`type_combinee`	No	EHF, requis si type_recherche=combinee. ciblee = recherche à l'intersection (débours forfait 12€ + 2€/élément au-delà de 5).
`type_recherche`	No	EHF uniquement : base de la recherche au SPF. cadastrale = par parcelles (ou lots si copropriété) ; identite = par personnes ; combinee = les deux.
`localisation_bien`	No	Commune avec code postal (ex. "34000 Montpellier"). NON requise pour le tarif public d'un état hypothécaire : le prix public est identique partout. Requise pour les packs et situation_patrimoine ; pour les abonnés, elle affine les débours en Alsace-Moselle.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

TDQS

A4.6/5.0

Behavior5/5

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

The description discloses read-only, no authentication, no personal data behavior, aligning with annotations (readOnlyHint=true, destructiveHint=false). It adds details about pricing calculation logic and conditions for accurate estimation, going beyond the annotations.

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?

The description is moderately long but each sentence adds value: purpose, safety, pricing details, parameter usage. It is front-loaded with the core purpose. Minor redundancy could be trimmed, but overall efficient.

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?

Given the tool's complexity (8 parameters, special EHF logic), the description covers purpose, safety, parameter usage hints, edge cases, and relationship to output schema (exists). It provides sufficient context for correct invocation.

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 coverage is 100%, so baseline is 3. The description adds significant value by explaining how EHF parameters (nb_parcelles, nb_lots, nb_personnes, type_recherche, etc.) affect pricing and provides usage tips (e.g., localisation_bien not required for public tariff).

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 tool provides the price (cost, tariff) for a HEL service, distinguishing it from siblings (orientation or subscription tariff tools). It specifies both public and reduced rates by subscription level.

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?

The description gives clear guidance on how to use parameters for accurate EHF quotes (e.g., providing type_recherche and counts for exact pricing) and explains the consequences of missing parameters. However, it does not explicitly state when not to use this tool versus alternatives.

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

All hel tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.5/5.0

Disambiguation5/5

Each tool has a clearly distinct purpose: one for service pricing, one for order links, one for service orientation by profession, and one for subscription tariffs. No overlap in functionality.

Naming Consistency5/5

All tools use the consistent 'hel-' prefix followed by a descriptive verb_noun pattern (devis-public, orienter-commande, orienter-service, tarifs-abonnements), making the purpose clear and predictable.

Tool Count5/5

With 4 tools, the server is well-scoped for providing pricing, ordering, and orientation information for HEL services. Each tool earns its place without redundancy.

Completeness4/5

The toolkit covers the core needs of pricing, ordering links, service orientation, and subscription info. Minor gap: no tool for basic service descriptions separate from pricing, but this is largely addressed by the orientation tool's URLs.

Resources

Need Help?