Skip to main content
Glama

Owid

by io.github.pipeworx-io

Get Indicator Metadata

get_indicator_metadata
Read-onlyIdempotent

Fetch chart metadata for an OWID indicator slug: title, subtitle, note, and per-column details (unit, description, data producer/citation, last_updated, next_update dates). Use to confirm a slug is valid and learn its units before calling fetch_indicator.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
slugYesOWID chart slug

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
noteYesAdditional note about the chart
slugYesOWID chart slug
titleYesIndicator chart title
columnsYesMetadata for each data column
subtitleYesChart subtitle or description
source_urlYesURL to the indicator on ourworldindata.org

Schema Changelog

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

  1. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "slug": "co-emissions-per-capita"
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "columns": {
+      "description": "Metadata for each data column",
+      "items": {
+        "properties": {
+          "citation": {
+            "description": "Citation information",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "description": {
+            "description": "Description of the column",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "key": {
+            "description": "Column identifier",
+            "type": "string"
+          },
+          "last_updated": {
+            "description": "Last update date",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "next_update": {
+            "description": "Expected next update date",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "producer": {
+            "description": "Data producer or source organization",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "title": {
+            "description": "Column title or name",
+            "type": "string"
+          },
+          "unit": {
+            "description": "Unit of measurement",
+            "type": [
+              "string",
+              "null"
+            ]
+          }
+        },
+        "required": [
+          "key",
+          "title",
+          "unit",
+          "description",
+          "producer",
+          "citation",
+          "last_updated",
+          "next_update"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "note": {
+      "description": "Additional note about the chart",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "slug": {
+      "description": "OWID chart slug",
+      "type": "string"
+    },
+    "source_url": {
+      "description": "URL to the indicator on ourworldindata.org",
+      "type": "string"
+    },
+    "subtitle": {
+      "description": "Chart subtitle or description",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "title": {
+      "description": "Indicator chart title",
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "required": [
+    "slug",
+    "source_url",
+    "title",
+    "subtitle",
+    "note",
+    "columns"
+  ],
+  "type": "object"
+}
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare idempotent, read-only, non-destructive. Description adds value by detailing return fields and usage context without contradicting annotations.

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 clear sentences: first lists return fields, second provides usage guidance. No extraneous information.

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 simple parameter, existing output schema, and annotations, the description sufficiently covers purpose, usage, and return structure.

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?

Only parameter slug with schema description 'OWID chart slug'; description says 'OWID indicator slug' which is nearly identical. Schema coverage is 100%, so description adds minimal additional meaning.

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?

Clearly describes fetching chart metadata for an OWID indicator slug, listing specific fields (title, subtitle, note, per-column details) and distinguishes from sibling fetch_indicator.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states when to use: 'Use to confirm a slug is valid and learn its units before calling fetch_indicator', providing clear context and alternative.

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

All Owid 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.

TDQS

A4.1/5.0
Disambiguation4/5

Most tools have clearly distinct purposes, but the multiple 'ask' variants (ask_pipeworx, ask_pipeworx_grounded, deep_research) and discovery tools (discover_tools, suggest_questions) could cause confusion. Descriptions help differentiate, but the overlap is notable.

Naming Consistency4/5

All tool names use lowercase with underscores, but there is a mix of verb-first (e.g., ask_pipeworx, fetch_indicator) and noun-first (e.g., ai_visibility_check, polymarket_arbitrage) patterns. Consistent style but varied structure.

Tool Count2/5

33 tools is excessive for a coherent set. The server covers diverse domains (data lookup, betting, memory, subscriptions, web generation, package scanning) without a clear unifying theme, making it feel like a collection of utilities rather than a focused tool surface.

Completeness3/5

Core data retrieval and research capabilities are well-covered, but there are notable gaps such as lack of data update tools for OWID and no direct visualization. Additionally, the betting tools are extensive while other areas like entity editing are missing.

Resources