Skip to main content
Glama

Mitoyens, pesticides près de chez vous

Profil d’un département

department_profile
Read-onlyIdempotent

Profil départemental : indice d’exposition, tonnages BNVD (CMR, herbicides, fongicides, insecticides), et profil de traitement par culture (IFT, fonction dominante, substances).

Source : Mitoyens (mitoyens.fr) — licence CC BY-NC 4.0 (usage non commercial). Parcelles RPG 2025 · Données BNVD 2024 arrêtées au 31 décembre 2024 · indice Rigal & Perrot, édition 2025 — données 2013-2022 · eau du robinet SISE-Eaux 2025.

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": {
      "dept": "<dept>"
    },
    "name": "department_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
deptYesCode département (ex. 33, 2A, 971).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / dept / description
      Previous value: -"Code département métropolitain (ex. 33)."New value: +"Code département (ex. 33, 2A, 971)."
  2. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already establish read-only, closed-world, idempotent behaviour, so the description is not carrying the safety burden. It adds substantive context the annotations cannot: the CC BY-NC 4.0 non-commercial licence restriction and the exact data vintages (BNVD 2024 as of 31 Dec 2024, Rigal & Perrot 2025 covering 2013-2022, SISE-Eaux 2025). What it does not state is anything about result size, units, or how the per-crop profile is structured.

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 first sentence front-loads the payload contents in a single dense enumeration, and the second block is a compact provenance/licence footer. Nothing is padded; the attribution line earns its place because it carries licence and vintage constraints.

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-parameter read tool with no output schema, the description covers what is returned (exposure index, tonnages by category, per-crop IFT profile) and the provenance and vintage of each dataset. Minor gaps remain: units for tonnages, the structure of the per-crop profile, and the exposure index scale are not explained.

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 coverage is 100% and the single 'dept' parameter is documented in the schema with examples including overseas codes. The description adds only the adjective 'départemental', which the parameter name and schema already convey, so 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 names the resource precisely ('Profil départemental') and enumerates the actual contents: exposure index, BNVD tonnages broken out by CMR/herbicides/fongicides/insecticides, and per-crop treatment profile with IFT, dominant function and substances. An agent can tell this is a department-level aggregated profile rather than a commune-level one, though it never explicitly contrasts itself with siblings like get_commune_exposure or compare_communes.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no exclusion of alternatives, and no prerequisites stated. The provenance paragraph tells the agent where the data comes from but nothing about when this tool is the right choice over the commune-level or ranking siblings.

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