hel

Orienter vers la page de service

hel-orienter-service

Read-only

À 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.

Input Schema

TableJSON 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

TableJSON Schema

Name	Required	Description	Default
No arguments

TDQS

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.

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?