hel

Orienter vers un service / une commande

hel-orienter-commande

Read-only

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.

Input Schema

TableJSON 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

TableJSON Schema

Name	Required	Description	Default
No arguments

TDQS

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.

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?