Skip to main content
Glama
Sign In
mcp-outremer

mcp-outremer

by Hug0x0
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

outremer_get_sources

Provides a curated list of official and high-value data sources for French overseas territories, covering national and local open-data portals.

Instructions

List curated official and high-value sources for Outre-mer.

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": "outremer_get_sources"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/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 full burden. It only says 'List' without disclosing whether this is a read-only operation, if it returns a fixed list or accepts filters, or any other behavior. No indication of network calls, caching, or response size.

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?

One concise sentence, no fluff, and it front-loads the key action. However, it is so minimal that it might be seen as under-specified rather than appropriately concise, but for a parameterless listing tool it is acceptable.

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?

Given no output schema, no annotations, and easy sibling confusion, the description is insufficient. It doesn't mention what kind of sources are returned (e.g., URLs, names, metadata), nor how it differs from other listing tools. Could benefit from a sample output or a note on scope.

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?

The tool has zero parameters and the schema coverage is 100% (empty object). The description adds a minimal value by clarifying that sources are 'curated official and high-value', which is not in the schema. With no params, a baseline of 4 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific action ('List curated official and high-value sources') with a resource ('Outre-mer'), but it lacks differentiation from sibling tools like outremer_search_data_gouv or outremer_list_reference_items. It is clear but does not distinguish what makes these sources unique versus other listing tools.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives. Sibling tools like outremer_search_data_gouv and outremer_list_reference_items could overlap, but no exclusions or context are provided. The description implies a static listing but gives no criteria for when to choose it.

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