Skip to main content
Glama
Sign In
ONS + Nomis MCP server

ONS + Nomis MCP server

by brynmrgn
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Remote

get_dataset

Retrieve metadata and the latest edition and version for a single dataset, including available download formats such as CSV and XLSX.

Instructions

Get a single dataset's metadata and its latest edition/version.

Follows the dataset's latest_version link so you get the concrete edition and version numbers needed by the downstream tools, plus the available download formats (csv, xlsx) for the whole dataset.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "dataset_id": "<dataset_id>"
    },
    "name": "get_dataset"
  }
}

Input Schema

NameRequiredDescriptionDefault
dataset_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

The description discloses that the tool follows the latest_version link internally and provides edition/version details and download formats. However, with no annotations, it lacks information on authentication requirements, error handling, or potential side effects.

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 concise sentences that front-load the main purpose and add necessary behavioral detail. Every sentence provides value without redundancy.

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?

For a simple tool with one parameter and an output schema, the description covers the core functionality and output. It misses potential information about error scenarios or prerequisites, but overall it is reasonably complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The single parameter dataset_id is not described in the schema or the tool description beyond its name. With 0% schema coverage, the description adds no meaningful semantics about the parameter's format or constraints.

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 clearly states it retrieves metadata and the latest edition/version of a dataset. The mention of following the latest_version link and providing download formats distinguishes it from some siblings like get_metadata, though it does not explicitly differentiate from all.

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?

The description implies the tool is used to obtain concrete edition/version numbers for downstream tools, but it does not provide explicit when-to-use or when-not-to-use guidance, nor does it list alternatives.

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