Skip to main content
Glama
Sign In

Data Newcaledonia

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Search Datasets

search_datasets
Read-onlyIdempotent

Search New Caledonia Open Data for datasets by keyword (government, environment, economy & geography). Returns dataset_ids (pass to query/dataset_info), titles, themes and record counts.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "economy trade"
    },
    "name": "search_datasets"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax datasets (1-100, default 20).
queryNoKeyword(s) to search dataset titles/descriptions.
offsetNoPagination offset (default 0).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent and open-world behavior, so safety is covered. The description adds genuinely useful behavior beyond that: it names the return shape (ids, titles, themes, record counts) and states the chaining contract to query/dataset_info, which no structured field provides.

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 compact sentences, front-loaded with the core action and scope, with the return-value and hand-off details trailing. No filler or repetition of schema content.

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?

With no output schema, the description usefully summarizes the return payload and the follow-on tools, which is enough for an agent to call and use it. Minor gap: no note on empty results or how keyword matching behaves across titles/descriptions.

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% and all three parameters (query, limit, offset) are documented in the schema with defaults and ranges. The description adds no syntax or format detail beyond the parenthetical theme hints, so the baseline 3 applies.

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?

States a concrete verb+resource+scope ('Search New Caledonia Open Data for datasets by keyword') and enumerates the returned fields. Naming query/dataset_info as downstream consumers distinguishes it from those siblings without needing their schemas.

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?

Usage is implied by the workflow hint ('dataset_ids to pass to query/dataset_info'), which tells the agent where this fits, but there is no explicit when-to-use statement, no when-not, and no guidance on choosing it over search_within or dataset_info.

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

All Data Newcaledonia toolsInspect
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