Othernet — La Réunion

government_enterprises_search

Read-onlyIdempotent

Search the official business directory. Text defaults to establishments in 974; direct SIREN/SIRET ignores geography. Read-only adapter. Cache 5min; stale replies are marked.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`q`	Yes
`page`	No
`limit`	No
`api_key`	No	Ask974.re agent token, used only by Ask974.re authorization. Never sent to the government provider.
`freshness`	No	fresh accepts unexpired cache or waits for a new collection; it never returns stale data.	allow_stale
`department`	No	French department code. Default 974 = La Réunion.	974

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 15, 2026

changedInput schema / properties / api_key / description

Previous value: -"othernet agent token, used only by othernet authorization. Never sent to the government provider."New value: +"Ask974.re agent token, used only by Ask974.re authorization. Never sent to the government provider."

Changed2 schema fields changedSep 13, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

addedInput schema / properties / freshness

Added value: +{
+  "default": "allow_stale",
+  "description": "fresh accepts unexpired cache or waits for a new collection; it never returns stale data.",
+  "enum": [
+    "allow_stale",
+    "fresh"
+  ],
+  "type": "string"
+}

First observedSep 12, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, and non-destructive behavior; the description adds valuable extras: cache 5min, stale replies are marked, and direct SIREN/SIRET bypasses geography. The statement 'Read-only adapter' aligns with the annotation, so there is no contradiction.

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?

The description is concise and front-loaded with the core purpose, then adds scoping and caching behavior. The phrase 'Read-only adapter' is slightly redundant with the readOnlyHint annotation, but it does not create meaningful padding.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the six parameters and the absence of an output schema, the description gives enough invocation context for most queries but never states what the search returns. An agent may need more explicit output details or result-shape information to confidently interpret the response.

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 50%, and the description clarifies the most significant parameter (q) by distinguishing text search vs SIREN/SIRET and the geography default. However, it does not add semantics for page or limit, which remain documented only by schema defaults and basic constraints.

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 states a specific action and resource: 'Search the official business directory.' It also adds useful scoping information about the 974 default and SIREN/SIRET behavior. However, it does not explicitly name or differentiate sibling tools such as government_address_search or government_communes_search.

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?

It gives an implied usage context: use it to search the official directory, with text defaulting to department 974 and direct identifier searches ignoring geography. It does not explicitly state when to choose this tool over its siblings or provide when-not-to-use conditions.

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

All Othernet — La Réunion 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?