search_datasetsSearch Réunion Open Data for datasets by keyword (regional services, transport, environment & economy). Returns dataset_ids (pass to query/dataset_info), titles, themes and record counts.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Max datasets (1-100, default 20). | |
| query | No | Keyword(s) to search dataset titles/descriptions. | |
| offset | No | Pagination offset (default 0). |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Input schema / examplesAdded value: +[
+ {
+ "query": "transport"
+ },
+ {
+ "limit": 10,
+ "offset": 0,
+ "query": "environment economy"
+ }
+]Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint as safe and idempotent. The description adds context about return values but does not disclose any additional behavioral traits beyond what annotations provide.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two sentences, front-loaded with the action, and contains no extraneous words. It is highly efficient.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The description covers the core functionality, return values, and how to use the results with sibling tools. With no output schema, it compensates by listing return elements. Slightly missing details on pagination, but those are covered in the schema.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, so all parameters are described. The description adds examples (e.g., 'transport', 'environment economy') that provide usage context, but does not add new semantic meaning beyond the schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool searches Réunion Open Data for datasets by keyword, lists example themes, and specifies the return values (dataset_ids, titles, themes, record counts). It also distinguishes from sibling tools by mentioning passing dataset_ids to query/dataset_info.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies when to use the tool (to search by keyword) and what to do with results (pass to query/dataset_info). However, it does not explicitly state when not to use it or provide alternatives.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.