Skip to main content
Glama

Ukhsa

by io.github.pipeworx-io
OverviewAdmin

List Metrics

list_metrics
Read-onlyIdempotent

Shortcut to list all available metric names for a fully-specified location — supply all five levels (theme, sub_theme, topic, geography_type, geography) at once rather than calling navigate iteratively. Returns metric names like "COVID-19_cases_casesByDay" ready to pass to get_metric_data.(theme, sub_theme, topic, geography_type, geography), without walking each level. Returns metric names like "COVID-19_cases_casesByDay" or "COVID-19_deaths_ONSByDay" ready to pass to get_metric_data.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
themeYese.g. "infectious_disease".
topicYese.g. "COVID-19".
geographyYese.g. "England".
sub_themeYese.g. "respiratory".
geography_typeYese.g. "Nation".

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "geography": "England",
+    "geography_type": "Nation",
+    "sub_theme": "respiratory",
+    "theme": "infectious_disease",
+    "topic": "COVID-19"
+  }
+]
  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, openWorldHint=true, idempotentHint=true, and destructiveHint=false, covering safety. The description adds that it returns metric names 'ready to pass to get_metric_data', which is useful but does not disclose additional behavioral traits like whether it caches or has rate limits.

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 two sentences, but the second sentence partially repeats the first. It is front-loaded with purpose and alternative, yet could be merged to remove 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?

Given no output schema, the description explains the return format (metric names like examples) and ties it to get_metric_data. It lacks mention of list size or pagination, but for a simple list tool, this is adequate. Sibling tools provide relevant context.

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 descriptions for all five parameters. The description restates them collectively as 'five levels' but adds no new semantic meaning beyond what the schema provides, so the baseline score of 3 applies.

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 it is a 'shortcut' to list all available metric names for a fully-specified location, avoiding iterative navigation via navigate. It explicitly names the output format (metric names ready for get_metric_data) and the five required levels, distinguishing it from sibling tools like navigate.

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 provides a clear 'when to use': when you have a fully-specified location, as an alternative to calling navigate iteratively. It does not explicitly list when not to use, but the context (seamless shortcut) is sufficient for an agent to decide.

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

All Ukhsa toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources