F
licenseA
qualityB
maintenanceProvides AI agents with real-time access to French real estate transaction data, price per square meter, and property estimates using official open DVF data, with no API key required.
4
hel
Server Details
Instant pricing for French land-registry documents (etat hypothecaire, deeds). Read-only, no auth.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
MCP client
Glama
MCP server
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
100% free. Your data is private.
Tool Definition Quality
A4.5/5.0
Tool DescriptionsA
Average 4.5/5 across 4 of 4 tools scored.
Server CoherenceA
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.
Available Tools
4 toolshel-devis-publicDevis public (tous niveaux)ARead-onlyInspect
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.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| 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
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
No output parameters | ||
Tool Definition Quality
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.
hel-orienter-commandeOrienter vers un service / une commandeARead-onlyInspect
Fournit les LIENS de page d'un service HEL : 'page_service_url' (page de présentation du service) et 'commande_directe_url' (formulaire de commande). N'effectue aucun calcul et ne renvoie aucun montant : pour un prix ou un devis chiffré, ce n'est pas cet outil. Services pris en charge : état hypothécaire, copie d'acte de vente, situation de patrimoine, règlement de copropriété, état descriptif de division, pré-état daté, packs, recherche de coordonnées propriétaire, vérification de mandat, RDV analyste, analyse IA, recherche de référence cadastrale. URL officielles exactes ; le paiement se fait sur le site.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| service | Yes | Service / document souhaité (texte libre). Ex. : état hypothécaire, copie d'acte, situation de patrimoine, règlement de copropriété, état descriptif de division, pré-état daté, pack propriété, pack règlement copropriété, pack EDD, recherche coordonnées propriétaire, vérification de mandat, RDV analyste, analyse IA, référence cadastrale. |
Output Schema
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
No output parameters | ||
Tool Definition Quality
A4.3/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate readOnlyHint and destructiveHint. Description adds that it performs no calculations, returns no amounts, and provides official URLs; payment occurs on the site. This provides useful behavioral context beyond annotations.
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?
Single paragraph, front-loaded with key output, each sentence adds value. No redundancy or unnecessary detail.
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?
With one parameter and existing output schema, the description fully explains what the tool returns, what it does not do, and which services it supports. Complete and sufficient.
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?
Schema description coverage is 100% and already lists examples. Main description repeats the list of supported services, adding minimal new meaning. Baseline 3 is appropriate.
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?
Description clearly states it provides links for HEL service pages and order forms ('Fournit les LIENS'). It distinguishes from pricing tools by explicitly excluding calculations and amounts. Lists supported services, making purpose 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?
Explicitly tells when not to use: 'pour un prix ou un devis chiffré, ce n'est pas cet outil.' Lists supported services, implying when it is appropriate. Does not directly name sibling tools but the context is clear.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
hel-orienter-serviceOrienter vers la page de serviceARead-onlyInspect
À partir de la profession du prospect (avocat, banque, courtier, syndic, agent ou agence immobilière, commissaire de justice / huissier, assurance, géomètre-expert, énergies renouvelables / solaire / éolien, marchand de biens, promoteur), renvoie l'URL de la page de service HEL adaptée — où le client découvre le service, souscrit son abonnement et passe commande. Pour un particulier ou une profession non listée, renvoie la page des tarifs professionnels. Renvoie l'URL officielle exacte de la page de service correspondante (présentation, tarifs, souscription et commande). Le paiement se fait sur le site.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| profession | Yes | Profession du prospect (texte libre). Valeurs typiques : Agents immobiliers, Assurances, Avocats, Banques & Courtiers, Commissaires de justice, Énergies renouvelables, Géomètres-experts, Marchands de biens, Promoteurs & autres, Syndics, Autre/particulier. |
Output Schema
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
No output parameters | ||
Tool Definition Quality
A4.5/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate readOnlyHint=true, and the description adds behavioral context: the tool returns an exact URL for a service page where payment occurs externally. No contradictions.
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, with two focused sentences that front-load the core action and provide necessary details without redundancy.
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 output schema exists (context signals), the description covers when to use, what it returns, and fallback logic. With good annotations, it is complete and leaves no critical gaps.
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%, and the description adds value by listing all valid profession categories and explaining the fallback behavior for unlisted professions, enhancing the parameter semantics beyond the schema.
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 verb (renvoie l'URL) and resource (page de service) and lists specific professions. It distinguishes from siblings like hel-devis-public and hel-orienter-commande by focusing on service page orientation, not quotes or orders.
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 explains when to use: to get a service page URL based on profession, including a fallback for individuals or unlisted professions. It implies alternatives with sibling names but does not explicitly state when not to use other tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
hel-tarifs-abonnementsTarifs des abonnementsARead-onlyInspect
Renvoie la grille des tarifs d'abonnement HEL (mensuel et annuel HT, conditions d'engagement) par niveau : Public, Essentiel, Privilège, Intégral. Aucun paramètre. Lecture seule, sans authentification ni donnée personnelle. Répond aux questions sur le coût des abonnements sans devis de service.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
Output Schema
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
No output parameters | ||
Tool Definition Quality
A4.7/5.0
Behavior5/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Beyond annotations (readOnlyHint, openWorldHint, destructiveHint), the description adds 'sans authentification ni donnée personnelle', clarifying no authentication needed and no personal data involved. It also states 'sans devis de service', preventing misuse. No contradictions with annotations.
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 two sentences, efficiently conveying purpose, scope, and constraints. No redundant information; every sentence adds value.
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 zero parameters and an output schema (implied), the description fully covers purpose, usage, and behavioral traits. It addresses cost questions without requiring service quotes, making it complete for this simple read-only tool.
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 tool has 0 parameters, so the baseline is 4. The description confirms no parameters via 'Aucun paramètre'. No additional semantic guidance is needed.
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 explicitly states it returns the HEL subscription tariff grid for four levels (Public, Essentiel, Privilège, Intégral), using specific verbs like 'Renvoie' and 'Répond aux questions sur le coût des abonnements'. It clearly distinguishes from siblings like hel-devis-public (for quotes) and hel-orienter-commande (for order orientation).
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 says 'Aucun paramètre' and 'sans devis de service', indicating it is for tariff inquiries only, not for service quotes. It implies when to use by stating it answers questions about subscription costs. However, it could explicitly mention alternatives (e.g., 'Use hel-devis-public for personalized quotes').
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!
Related MCP Servers
- AlicenseAqualityFmaintenanceFrench building permits MCP server: 1.2M Sitadel permits (2014-2026, daily refresh), DVF transactions, cadastre DGFiP, PLU zoning, BRGM risks, and property-dealer opportunity scoring through 11 MCP tools. Free tier 500 req/month, no credit card.113MIT
- Flicense-qualityCmaintenanceProvides French address data from DVF, Géorisques, and SSMSI sources, including property prices, risks, and crime statistics.
- Flicense-qualityFmaintenanceFrench real estate data platform for AI agents. Identifies property owners likely to sell and tracks behavioral signals on active listings. Coverage: metropolitan France.