Skip to main content
Glama
Sign In
mcp-mayotte

mcp-mayotte

by Hug0x0
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

mayotte_search_data_gouv

Search public datasets from data.gouv.fr using the official API. Enter a query and set page size to find relevant Mayotte public data and administrative references.

Instructions

Search public datasets on data.gouv.fr using the official public API.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "mayotte_search_data_gouv"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNoSearch query.Mayotte
page_sizeNoNumber of datasets to return.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden for behavioral disclosure. It states the operation is a search via the official public API, implying read-only access, but it does not mention return format, pagination behavior, or any limitations.

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 a single sentence that directly states the tool's purpose without fluff or redundancy.

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

Completeness2/5

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

The tool has no output schema, so the description should ideally clarify what the search returns. It also doesn't differentiate from the sibling mayotte_search_datasets, leaving ambiguity. For a simple two-parameter tool, key contextual details are missing.

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% for both parameters (query and page_size). The description adds no extra parameter semantics, but the schema already documents each parameter adequately, so the baseline of 3 applies.

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 specifies the verb 'search' and resource 'public datasets on data.gouv.fr', with the additional detail of the official public API. It clearly indicates the tool's function, though it doesn't explicitly distinguish from the similarly named sibling mayotte_search_datasets.

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?

The description gives clear context: use this tool to search for public datasets specifically on data.gouv.fr. It does not discuss when to prefer alternatives or any exclusions, but the context is unambiguous.

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

Deploy Server

Other Tools