CreditLabs

get_ptz_zone

Recherche la zone ABC d'une commune française par son code INSEE. Zonage officiel au 26 juin 2026, pas une décision d'éligibilité PTZ.

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": {
      "codeInsee": "<codeInsee>"
    },
    "name": "get_ptz_zone"
  }
}

Input Schema

Name	Required	Description	Default
`codeInsee`	Yes	Code INSEE (5 caractères, y compris 2A/2B).

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 10, 2026

TDQS

A3.8/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It does disclose two genuinely useful traits beyond the schema: the data is an official zonage versioned 'au 26 juin 2026', and it is explicitly not an eligibility determination — a scope limit that prevents misuse. It says nothing about behavior for invalid/unknown INSEE codes, return shape, or data source authority, which leaves a real gap for an unannotated tool.

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?

Two tight sentences: the capability and its key are front-loaded, and the disclaimer follows as a scoping caveat. Every clause carries information; nothing is redundant.

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 lookup with a fully documented schema, the description covers the essential context: what is returned (an ABC zone), the freshness of the underlying zonage, and the boundary of the claim (not an eligibility decision). Minor gap: with no output schema, it does not indicate the expected zone values or the response for an unfound commune.

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 single parameter already documents the 5-character INSEE format including 2A/2B. The description only restates that the lookup is by INSEE code, adding no format, casing, or validity detail beyond the schema — baseline 3 applies.

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?

States a specific verb ('Recherche'), a specific resource ('la zone ABC d'une commune française') and the lookup key ('par son code INSEE'). The closing clause 'pas une décision d'éligibilité PTZ' implicitly separates it from the sibling 'estimate_ptz', so an agent can route between zonage lookup and eligibility estimation.

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: the negation 'pas une décision d'éligibilité PTZ' signals this tool is for zoning lookup rather than eligibility, which points an agent toward estimate_ptz for the latter. There is no explicit when-to-use statement, no prerequisite (e.g. obtaining an INSEE code) and no error guidance for unknown communes.

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

All CreditLabs 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?