Skip to main content
Glama
Sign In

LegalOne Entreprises

by fr.legalone
OverviewDiscussionsAdmin

Normalize a French postal address

search_addresses
Read-onlyIdempotent

Use this when the user gives a French postal address, complete or partial, and wants it checked, completed, normalized or geolocated: returns the best Base Adresse Nationale matches with house number, street, postcode, city, INSEE municipality code, coordinates and a match score, plus whether the best match is reliable. Do not use for addresses outside France, for finding who lives or works at an address, or for listing the companies at an address.

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": {
      "address": "<address>"
    },
    "name": "search_addresses"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
addressYesPostal address, e.g. 8 bd du Port Amiens.
postcodeNoOptional 5-digit postcode to narrow the search.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly/openWorld/idempotent/non-destructive, so safety is covered. The description usefully adds return content and the 'whether the best match is reliable' signal, which matters for deciding whether to trust results. It omits any note on rate limits, coverage caveats of the BAN dataset, or what happens when no match is found.

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 sentences, usage condition front-loaded before exclusions, no filler. The return-field enumeration is long but justified because no output schema exists. Slightly dense but every clause carries selection value.

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?

With no output schema, the description carries the burden of describing return values and does so thoroughly, including the reliability judgment. Minor gap: no mention of `limit` semantics or empty-result behavior, which an agent would want before tuning a query.

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 67% and the schema already documents address and postcode examples. The description adds no guidance on what `limit` controls or how partial addresses interact with postcode narrowing, so it does not compensate for the remaining gap. Baseline 3 given the mid-level coverage.

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 and resource (normalize/geolocate a French postal address) and enumerates the returned fields (BAN matches, INSEE code, coordinates, match score, reliability flag). It is clearly distinguishable from siblings like search_companies or get_establishment, which answer different questions.

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

Usage Guidelines5/5

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

Explicit when-to-use ('user gives a French postal address, complete or partial, and wants it checked, completed, normalized or geolocated') plus three explicit exclusions: non-French addresses, finding residents, and listing companies at an address. That routes the agent away from search_companies and directory-style siblings.

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

All LegalOne Entreprises 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