Skip to main content
Glama

Lister les calculateurs et simulateurs

list_calculators
Read-onlyIdempotent

Liste les 69 calculateurs et simulateurs gratuits de Vitef (salaire, chômage, impôt, prêt, préavis, indemnités, TVA, dates, trajets, prix au kilo…), avec leur identifiant (slug).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_calculators"
  }
}

Input Schema

NameRequiredDescriptionDefault
groupNoFiltrer par groupe (Travail, Argent, Logement, Dates, Auto & trajets, Quotidien, Impôts & aides).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds useful non-schemaed context (the catalog is fixed at 69 free calculators), but says nothing about result ordering, pagination, or response shape beyond the slug field, so it adds modest value above 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?

A single front-loaded sentence with the verb and scope first, followed by illustrative domain examples that help match a user's phrasing. The long parenthetical enumeration is slightly padded but each example aids retrieval, so it 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?

For a one-optional-parameter, read-only listing tool with full annotation coverage and no output schema, the description supplies what an agent needs: what the list contains, its size, and the identifier it returns. Only minor gaps remain, such as ordering of results and an explicit pointer to the consuming tools.

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%: the single optional `group` parameter already spells out the seven allowed group values in the schema. The description never mentions filtering by group at all, so it adds no meaning beyond the schema and the baseline of 3 applies.

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 opens with a specific verb and resource ("Liste les 69 calculateurs et simulateurs gratuits de Vitef") and enumerates the domains covered, so an agent knows exactly what catalog is returned. It also states the payload includes each calculator's slug, which distinguishes it from the lookup/execution siblings get_calculator and compute_calculator, though those are never named explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: by advertising that results carry a slug, it hints this is a discovery step preceding get_calculator or compute_calculator, but it never says so. There is no explicit when-to-use, when-not-to-use, or named alternative.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources