Skip to main content
Glama

TOISE — intelligence foncière

Référentiels, couverture des données et étude partagée

toise_referentiels
Read-onlyIdempotent

Quelles valeurs sont acceptées par les outils TOISE : métiers, codes NAF, catégories, vocabulaire. Modes vocabulaire (métiers et clés de choix du bilan), criteres, categories, couverture, etude_partagee.

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": {
      "mode": "<mode>"
    },
    "name": "toise_referentiels"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeYesRéférentiel demandé : vocabulaire…
jetonNoMode etude_partagee : jeton du lien de…

Output Schema

NameRequiredDescriptionDefault
modeYes
liensNoLiens vers la fiche TOISE et vers des services de…
quotaNoQuota du jour après cet appel : { fonction, limite…
totalYesNombre d’entrées du référentiel rendu…
curseurYes
partielNotrue : une source n’a pas répondu, des champs manquent…
sourcesYes
has_moreYes
resultatYesContenu propre au mode : vocabulaire { metiers, programmes…
warningsYes
quota_unitesNoUnités d’usage du jour : consommees_par_cet_appel…
champs_absentsNoDonnées absentes du résultat partiel.
limite_atteinteNoPrésent quand un quota, une limite d’offre ou une fonction…
paiement_requisNoPrésent quand le résultat complet est un achat à l’acte…

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / jeton / description
      Previous value: -"Mode etude_partagee : jeton du lien de partage…"New value: +"Mode etude_partagee : jeton du lien de…"
    • changedInput schema / properties / mode / description
      Previous value: -"Référentiel demandé : vocabulaire, criteres…"New value: +"Référentiel demandé : vocabulaire…"
  2. 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=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds only the domain coverage of the returned referentials and one hint about vocabulaire contents; it says nothing about result size, whether values are versioned, or how etude_partagee behaves beyond the schema's jeton field.

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?

Two short sentences, front-loaded with the core question the tool answers. The second sentence is largely a restatement of the mode enum, which slightly dilutes its value, but the definition stays compact and free of filler.

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?

An output schema exists, so return values need not be described, and the read-only nature is covered by annotations. What remains missing is modest: guidance on which mode to pick and confirmation that etude_partagee requires the jeton. For a two-parameter reference-lookup tool, the definition is essentially 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 the mode enum is fully enumerated with per-value descriptions, so the schema carries the parameter burden. The description contributes one genuine addition beyond it — that vocabulaire covers métiers and the `choix` keys of the bilan — which earns it no more than the baseline of 3.

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 concrete framing (which values are accepted by the TOISE tools) and enumerates the reference domains covered: métiers, codes NAF, catégories, vocabulaire. That is enough to distinguish it from sibling analysis tools, which consume these values rather than return them. It stops short of a clean verb+resource statement, since 'Quelles valeurs sont acceptées' is a question rather than a declaration of what the tool returns.

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?

Listing the modes implicitly tells the agent this is a lookup tool to consult when a valid value is needed, and the parenthetical on vocabulaire hints at its role for the bilan `choix` keys. However, there is no explicit when-to-use guidance, no statement that it should be called before tools that take métiers/NAF codes, and no differentiation among the five modes beyond their names.

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