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.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "service": "<service>"
    },
    "name": "hel-orienter-commande"
  }
}

Input 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

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedSep 10, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```
- addedOutput schema / description
```
Added value: +"service_detecte, intitule, page_service_url, commande_directe_url."
```
- addedOutput schema / properties
```
Added value: +{}
```
Changed3 schema fields changedSep 10, 2026
- removedInput schema / additionalProperties
```
Removed value: -false
```
- removedOutput schema / description
```
Removed value: -"service_detecte, intitule, page_service_url, commande_directe_url."
```
- removedOutput schema / properties
```
Removed value: -{}
```
Changed3 schema fields changedSep 9, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```
- addedOutput schema / description
```
Added value: +"service_detecte, intitule, page_service_url, commande_directe_url."
```
- addedOutput schema / properties
```
Added value: +{}
```
First observedJul 6, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already carry readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds value beyond annotations by disclosing that the tool performs no calculation, returns no amounts, supplies exact official URLs, and that payment happens on the external site—clarifying what the tool does and does not do. No contradiction 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with purpose, then the exclusion clause, then the service list, then URL/payment details. It is longer than minimal, but the extended service catalog is justified given openWorldHint=true and a free-text parameter. Every sentence earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present to document return values and only one simple parameter, the description covers the essential operational facts: returned fields, supported services, exclusions, and payment behavior. The only notable gap is the missing explicit relationship to the hel-orienter-service sibling.

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 the single 'service' parameter is already documented with examples. The description reinforces this by enumerating the full supported service catalog in free text, adding meaningful scope context for an open-world parameter beyond what the schema examples provide.

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?

The description states a specific action (provides page links: page_service_url and commande_directe_url) and enumerates the supported service catalog. It clearly distinguishes itself from pricing/quote tools ('ne renvoie aucun montant'). However, it does not differentiate from the near-twin sibling hel-orienter-service, which likely returns the same presentation-page link, leaving potential 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?

Provides an explicit exclusion clause ('pour un prix ou un devis chiffré, ce n'est pas cet outil') that routes agents away from pricing use cases toward quote/rate siblings. However, it never names the alternatives nor clarifies when to choose this tool over hel-orienter-service versus hel-devis-public, leaving the primary routing decision implicit.

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

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?