Skip to main content
Glama

HelpMyAgent

by io.github.helpmyagent
OverviewDiscussionsAdmin

French Cadastral Parcel

real_estate_fr_parcel

Identifies French cadastral parcels by address point or cadastral municipality/section/number and returns official IGN geometry. Use when: Identify a French cadastral parcel and retrieve its geometry. Avoid when: Do not treat this as a legally opposable property-title document. Limitations: Address search intersects the geocoded point with cadastral geometry and can return multiple parcels on a parcel boundary. Price: 0.010 USD per call via x402. Paid-call behavior: source records are not modified, but a successful invocation can consume the advertised x402 payment; the payment-required challenge is free, and repeating the tool after a completed paid invocation may require a new payment. Accepted x402 networks: eip155:8453, xrpl:0.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
numeroNoOptional value for “numero” as defined by this API contract.
addressNoOptional value for “address” as defined by this API contract. (minimum length 5; maximum length 250).
sectionNoOptional value for “section” as defined by this API contract.
code_inseeNoOptional value for “code insee” as defined by this API contract.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
bboxYesStructured value returned for “bbox” as defined by this API contract.
parcelsYesStructured value returned for “parcels” as defined by this API contract.
locationYesStructured value returned for “location” as defined by this API contract.
limitationsNoKnown interpretation, source-coverage or freshness limitations for this result.
total_countYesTotal number of matching records reported by the source or endpoint.
generated_atYesUTC timestamp at which this derived result was generated.
source_statusYesAvailability status of the relevant upstream public source. (allowed values: ok).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / required
      Previous value: -[
-  "location",
-  "source_status",
-  "total_count",
-  "parcels",
-  "bbox",
-  "generated_at",
-  "limitations"
-]New value: +[
+  "location",
+  "source_status",
+  "total_count",
+  "parcels",
+  "bbox",
+  "generated_at"
+]
  2. Added

TDQS

A4.5/5.0
Behavior5/5

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

Annotations are all false and provide no safety hints, so the description carries the full burden. It discloses that source records are not modified, details the x402 paid-call behavior (payment consumption, free challenge, potential new payment on repeat), and warns of multiple parcels on boundary intersections. This is thorough and goes beyond the annotation defaults.

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 description is structured with clear sections (Use when, Avoid when, Limitations, Price, Paid-call behavior, Accepted networks) and front-loads the core purpose. Every sentence adds information, including pricing and network details, with no filler.

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?

Given an output schema exists (the tool returns IGN geometry, likely defined there), the description covers what the tool does, how to invoke it, limitations, pricing, payment behavior, and supported networks. An agent has everything needed to decide when to call and what to expect.

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%, but the per-parameter descriptions are generic ('Optional value for ... as defined by this API contract'). The tool description clarifies the two parameter groups (address vs. code_insee+section+numero) and mentions the cadastral reference, adding modest value over the schema. Baseline 3 is appropriate since the schema already covers syntax via patterns.

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?

The description opens with a specific verb ('Identifies') and a clear resource (French cadastral parcels), and states the two lookup methods (address or municipality/section/number) plus the output (official IGN geometry). It is distinct from sibling real-estate tools, which cover DPE, market, risks, transactions, and valuation.

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?

Explicit 'Use when' states the intended invocation scenario. The 'Avoid when' warns against legal use but does not name an alternative tool; however, among the siblings there is no direct substitute for parcel identification, so the guidance is adequate.

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

All HelpMyAgent 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