Skip to main content
Glama

Entreprises Fr

by io.github.pipeworx-io
OverviewAdmin

Nearby

nearby
Read-onlyIdempotent

List French business establishments within a radius (0.05–50 km) of a lat/lon coordinate. Optionally filter by APE/NAF sector code. Returns SIREN, denomination, addresses, and sector codes for each nearby unit.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
apeNoFilter to a specific APE/NAF code
pageNo1-based page (default 1)
latitudeYesLatitude (WGS84)
per_pageNoPage size, 1-25 (default 10)
longitudeYesLongitude (WGS84)
radius_kmNoSearch radius in km, 0.05-50 (default 1)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoCurrent page number
resultsNoArray of nearby establishments
per_pageNoResults per page
total_resultsNoTotal number of nearby establishments

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "latitude": 48.8566,
+    "longitude": 2.3522
+  },
+  {
+    "ape": "4711Z",
+    "latitude": 43.2965,
+    "longitude": 5.3698,
+    "radius_km": 5
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "page": {
+      "description": "Current page number",
+      "type": "number"
+    },
+    "per_page": {
+      "description": "Results per page",
+      "type": "number"
+    },
+    "results": {
+      "description": "Array of nearby establishments",
+      "items": {
+        "properties": {
+          "address": {
+            "description": "Establishment address",
+            "type": "string"
+          },
+          "ape": {
+            "description": "APE/NAF activity code",
+            "type": "string"
+          },
+          "city": {
+            "description": "City name",
+            "type": "string"
+          },
+          "denomination": {
+            "description": "Establishment or unit name",
+            "type": "string"
+          },
+          "distance_km": {
+            "description": "Distance from search center in km",
+            "type": "number"
+          },
+          "enseigne": {
+            "description": "Trading name",
+            "type": "string"
+          },
+          "etat_administratif": {
+            "description": "Status (A=active, R=closed)",
+            "type": "string"
+          },
+          "latitude": {
+            "description": "WGS84 latitude",
+            "type": "number"
+          },
+          "longitude": {
+            "description": "WGS84 longitude",
+            "type": "number"
+          },
+          "postal_code": {
+            "description": "5-digit postal code",
+            "type": "string"
+          },
+          "siren": {
+            "description": "9-digit SIREN of parent unit",
+            "type": "string"
+          },
+          "siret": {
+            "description": "14-digit SIRET identifier",
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "total_results": {
+      "description": "Total number of nearby establishments",
+      "type": "number"
+    }
+  },
+  "type": "object"
+}
  2. First observed

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint, so the safety profile is well-covered. The description adds context about the return fields and range constraints, providing moderate additional value.

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 concise sentences that front-load the key action and results. Every sentence is informative and no 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?

Covers the main functionality, filters, radius range, and return fields. Pagination parameters are in the schema but not in the description, which is acceptable given the output schema exists. Adequate for a search tool with rich annotations.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with descriptions for each parameter. The description adds meaning by stating the purpose of the radius and APE filter, and specifying the returned fields, which goes beyond the schema's individual parameter descriptions.

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?

Description clearly states the tool lists French business establishments within a radius, with optional filtering by APE/NAF sector code, and specifies the returned data fields (SIREN, denomination, addresses, sector codes). This is a specific verb+resource and distinguishes from sibling tools.

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?

Description clearly indicates when to use: to find nearby French business establishments. It does not explicitly mention when not to use or alternative tools, but the context is clear enough for a simple search tool.

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

All Entreprises Fr toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources