Skip to main content
Glama
Sign In

Data Newcaledonia

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Dataset Info

dataset_info
Read-onlyIdempotent

Get metadata for one New Caledonia Open Data dataset (fields/schema, themes, record count) — call before query to learn the column names.

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": {
      "dataset_id": "new-caledonia-gdp-by-sector"
    },
    "name": "dataset_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
dataset_idYesDataset id from search_datasets.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and openWorld, so the safety profile is covered. The description adds value by disclosing what the call returns (schema, themes, record count) for a tool with no output schema, though it says nothing about pagination, rate limits, or error behavior for missing ids.

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?

One tight sentence plus a purpose clause; the resource scope is front-loaded and every phrase (fields/schema, themes, record count, pre-query usage) carries information. No filler.

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

Completeness5/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 compensates by naming the returned metadata fields, and the required pre-query sequencing is stated. An agent has everything needed to call this correctly.

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 the single parameter is already documented as 'Dataset id from search_datasets'. The description adds no syntax, format, or constraint information beyond the schema, 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 specific verb (Get metadata), a specific resource (one New Caledonia Open Data dataset), and enumerates the returned content (fields/schema, themes, record count). This clearly distinguishes it from siblings like search_datasets (plural discovery) and query (data retrieval).

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?

Explicitly instructs the agent to call it before query in order to learn column names, which is a concrete usage trigger. It doesn't state when-not to use it or name an alternative tool outright, but the sequencing guidance is clear.

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