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

ONS + Nomis MCP server

by brynmrgn
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Remote

nomis_data_url

Generate a direct download URL for bulk Nomis data retrieval, supporting CSV, XLS, and JSON formats with time and list syntax in dimensions.

Instructions

Build a direct Nomis download URL for bulk retrieval.

For large pulls it's often better to hand back a URL than to stream every observation through the model. Returns a ready-to-use link in the requested format (csv, xls, data.json). Nomis time and list syntax is supported in dimensions values.

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>",
      "dimensions": "<dimensions>"
    },
    "name": "nomis_data_url"
  }
}

Input Schema

NameRequiredDescriptionDefault
fmtNocsv
dataset_idYes
dimensionsYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

With no annotations, the description explains it returns a URL (read-only) and supports specific formats and dimensions syntax, but lacks details on authentication, rate limits, or whether the URL is temporary.

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 sentences, front-loaded with purpose, every sentence adds value with zero waste.

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 an output schema exists, the description covers the main return type (URL) and key behaviors (format, dimensions), but could be more complete about parameter details and URL lifetime.

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 0%, so the description partially compensates by mentioning formats for 'fmt', implying 'dataset_id', and explaining 'dimensions' supports time and list syntax, but doesn't fully detail each parameter's meaning or constraints.

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?

The description clearly states the tool builds a Nomis download URL for bulk retrieval, listing supported formats (csv, xls, data.json) and syntax support, distinguishing it from siblings that stream data.

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?

The description gives guidance to use this tool for large pulls to avoid streaming, but doesn't explicitly mention when not to use it or name alternative tools.

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