Skip to main content
Glama
Sign In

Uk Ons

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Get Version

get_version
Read-onlyIdempotent

Fetch metadata for a specific version of an ONS dataset edition, including dimension definitions with codelist links, CSV/XLS download URLs, release date, and publication state.

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": {
      "edition": "time-series",
      "version": "1",
      "dataset_id": "cpih01"
    },
    "name": "get_version"
  }
}

Input Schema

NameRequiredDescriptionDefault
editionYesEdition label
versionYesVersion (e.g., "1", "2")
dataset_idYesONS dataset ID

Output Schema

NameRequiredDescriptionDefault
stateYesVersion state
editionYesEdition label
versionYesVersion number
downloadsYesDownload links for different formats
dataset_idYesDataset ID
dimensionsYesDimension definitions
release_dateYesRelease date

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "dataset_id": "cpih01",
+    "edition": "time-series",
+    "version": "1"
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "dataset_id": {
+      "description": "Dataset ID",
+      "type": "string"
+    },
+    "dimensions": {
+      "description": "Dimension definitions",
+      "items": {
+        "properties": {
+          "id": {
+            "description": "Dimension ID",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "label": {
+            "description": "Dimension label",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "name": {
+            "description": "Dimension name",
+            "type": [
+              "string",
+              "null"
+            ]
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "downloads": {
+      "description": "Download links for different formats",
+      "properties": {
+        "csv": {
+          "description": "CSV download link",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "csvw": {
+          "description": "CSVW download link",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "xls": {
+          "description": "XLS download link",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "xlsx": {
+          "description": "XLSX download link",
+          "type": [
+            "string",
+            "null"
+          ]
+        }
+      },
+      "type": "object"
+    },
+    "edition": {
+      "description": "Edition label",
+      "type": "string"
+    },
+    "release_date": {
+      "description": "Release date",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "state": {
+      "description": "Version state",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "version": {
+      "description": "Version number",
+      "type": "integer"
+    }
+  },
+  "required": [
+    "dataset_id",
+    "edition",
+    "version",
+    "state",
+    "release_date",
+    "dimensions",
+    "downloads"
+  ],
+  "type": "object"
+}
  2. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true. The description adds that the tool fetches metadata with specific fields, which does not contradict annotations but also does not significantly enhance behavioral transparency beyond what annotations provide.

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?

The description is a single concise sentence that efficiently lists the return contents. No extraneous words.

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?

Given the tool has a clear purpose, comprehensive annotations, and an output schema (not shown but exists), the description is complete. It covers what the tool does and what it returns, leaving no obvious gaps.

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 100% with brief descriptions. The description does not add any additional parameter semantics beyond what is in the schema. Baseline score of 3 is appropriate since the schema already covers the parameters.

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 verb 'Fetch' and the resource 'metadata for a specific version of an ONS dataset edition', listing included elements. This differentiates it from siblings like 'get_dataset' (which likely fetches dataset-level metadata) and 'list_editions'.

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 use when you need metadata for a specific version, but does not explicitly state when not to use it or suggest alternatives. Given the sibling tools list includes 'get_observations' and 'list_editions', some guidance on scope would help.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Uk Ons 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