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

ONS + Nomis MCP server

by brynmrgn
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Remote

list_datasets

Browse and retrieve a paginated list of available ONS datasets, including titles, descriptions, and edition links.

Instructions

List available ONS datasets (paginated).

Returns id, title, description, release_frequency and the latest edition/version links for each dataset. Use offset to page through the full catalogue (there are several hundred datasets).

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

Input Schema

NameRequiredDescriptionDefault
limitNo
offsetNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior3/5

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

No annotations are present, so the description must fully disclose behavior. It explains the return fields and pagination, but does not mention authentication, rate limits, or that it is a safe read operation. Adequate but not thorough.

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 short sentences convey the tool's purpose and key details without unnecessary words. Each sentence adds value.

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?

Given the output schema covers return structure, the description is mostly complete. It could mention pagination mechanism details, but overall it's sufficient for a simple listing tool.

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?

Schema description coverage is 0%, so the description must compensate. It only explains offset for pagination but does not describe limit or defaults, leaving half the parameters insufficiently documented.

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?

Description clearly states 'List available ONS datasets' and mentions pagination, making the action and resource explicit. It distinguishes itself from siblings like search_datasets by being a general listing.

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?

Provides guidance on using offset for pagination, implying the tool lists all datasets. However, it lacks explicit when-not-to-use or alternatives, though sibling names suggest search functions for specific queries.

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