Skip to main content
Glama

hel

by fr.hypotheques-en-ligne
OverviewDiscussionsAdmin

Tarifs des abonnements

hel-tarifs-abonnements
Read-only

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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties
      Added value: +{}
    • addedOutput schema / description
      Added value: +"Grille d'abonnements par niveau : mensuel_ht, annuel_ht, engagement + note TVA."
    • addedOutput schema / properties
      Added value: +{}
  2. Changed4 schema fields changed
    • removedInput schema / additionalProperties
      Removed value: -false
    • removedInput schema / properties
      Removed value: -{}
    • removedOutput schema / description
      Removed value: -"Grille d'abonnements par niveau : mensuel_ht, annuel_ht, engagement + note TVA."
    • removedOutput schema / properties
      Removed value: -{}
  3. Changed4 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties
      Added value: +{}
    • addedOutput schema / description
      Added value: +"Grille d'abonnements par niveau : mensuel_ht, annuel_ht, engagement + note TVA."
    • addedOutput schema / properties
      Added value: +{}
  4. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Beyond the readOnly/openWorld annotations, the description adds that the call requires no authentication and involves no personal data. A low-risk, static lookup tool, but the extra behavioral context is useful.

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?

Three short sentences deliver purpose, content, scope, and usage conditions. No filler or repetition beyond the necessary explicit statement that there are no parameters.

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?

For a parameterless read-only pricing tool, this covers what is returned, the granularity (monthly/annual, excl. tax), the tiers, authentication expectations, and the boundary against quote requests. No meaningful gap remains.

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 schema has zero parameters. The description explicitly states 'Aucun paramètre', which is appropriate and avoids any illusion of inputs needing to be supplied.

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?

Uses a specific verb and resource ('Renvoie la grille des tarifs'), lists the exact tiers, and states the price dimensions (mensuel et annuel HT). It clearly distinguishes itself from quote/order tools by noting it is not a service quote.

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?

Gives a clear usage context: answering subscription-cost questions without producing a service quote. It does not explicitly name the sibling tool for quotes, but the exclusion is sufficient guidance for routing.

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

All hel toolsInspect
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