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

ONS + Nomis MCP server

by brynmrgn
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Remote

get_topic_content

List published content like bulletins, articles, key time series, and dataset pages under a topic. Use the topic ID to browse items and directly access time series data.

Instructions

List the content published under a topic (bulletins, articles, key time series, dataset pages).

topic_id is the numeric id from list_topics (e.g. "4972" = Inflation and price indices). Items carry a type and title; where an item is a published time series, timeseries_uri is filled in ready to pass straight to get_timeseries. A convenient bridge from a topic to the headline series under it.

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": {
      "topic_id": "<topic_id>"
    },
    "name": "get_topic_content"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
offsetNo
topic_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are provided, so the description carries full burden. It discloses the output structure (type, title, timeseries_uri) but does not mention behavioral traits like read-only status, error handling, required permissions, or side effects. For a read-like tool, the lack of transparency is a significant gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise, with two sentences that front-load the action and purpose. It efficiently explains the main behavior and a key output detail without unnecessary words. Minor downside: lack of parameter descriptions consumes a bit of clarity.

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

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the existence of an output schema (context: true), the description appropriately avoids detailing return values. It covers the core purpose and the most important parameter. However, it omits discussion of pagination (limit/offset) and usage boundaries, leaving some gaps for an agent.

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 coverage is 0%, so the description must compensate. It adds meaning for topic_id (numeric id from list_topics with an example) and mentions timeseries_uri as a bridge. However, limit and offset parameters are not explained, leaving them to be inferred as pagination defaults.

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 the tool lists content under a topic, specifying content types (bulletins, articles, key time series, dataset pages). It explains the topic_id parameter and the output fields (type, title, timeseries_uri). However, it does not explicitly distinguish itself from sibling tools like get_timeseries or list_topics, missing a clear differentiation.

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 provides some context: topic_id comes from list_topics, and the tool is a bridge to get_timeseries via timeseries_uri. But it lacks explicit guidance on when to use this tool versus alternatives (e.g., searching content by other criteria) and does not state when not to use it.

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