Skip to main content
Glama

Owid

by io.github.pipeworx-io

List Popular Indicators

list_popular_indicators
Read-onlyIdempotent

List curated Our World in Data indicators (slug + title) for common categories: energy, climate, health, demographics, economy, food, education, environment, tech, politics. Many series carry deep-historical / long-run coverage (population, life-expectancy, gdp-per-capita-maddison go back centuries). Use the slug with fetch_indicator. Not exhaustive — visit ourworldindata.org for the full catalog.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
categoryNoOptional category filter

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
noteYesUsage note directing users to the full OWID catalog
countYesNumber of indicators in the filtered result
indicatorsYes

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: +[
+  {
+    "category": "energy"
+  },
+  {
+    "category": "climate"
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "count": {
+      "description": "Number of indicators in the filtered result",
+      "type": "number"
+    },
+    "indicators": {
+      "items": {
+        "properties": {
+          "category": {
+            "description": "Category classification (energy, climate, health, etc.)",
+            "type": "string"
+          },
+          "slug": {
+            "description": "OWID chart slug identifier",
+            "type": "string"
+          },
+          "title": {
+            "description": "Human-readable indicator title",
+            "type": "string"
+          }
+        },
+        "required": [
+          "slug",
+          "title",
+          "category"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "note": {
+      "description": "Usage note directing users to the full OWID catalog",
+      "type": "string"
+    }
+  },
+  "required": [
+    "count",
+    "note",
+    "indicators"
+  ],
+  "type": "object"
+}
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint. The description adds that the tool returns slug+title, is curated, and not exhaustive, providing useful behavioral context beyond 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?

The description is two concise sentences. The first clearly states the action and content, while the second adds nuance and cross-reference. No unnecessary 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 it is a simple list tool with an output schema, the description covers purpose, output details, limitations (not exhaustive), and how to use with another tool. It is complete and actionable.

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?

With 100% schema coverage and an enum parameter, the description adds minimal extra meaning—only listing example categories that match the enum. Baseline of 3 is appropriate as the schema already documents the parameter fully.

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 'List' and the resource 'curated Our World in Data indicators'. It specifies the output (slug + title) and common categories, effectively distinguishing it from siblings like fetch_indicator or get_indicator_metadata.

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 context on when to use: for common categories and long-run coverage. It also directs users to visit the website for full catalog and mentions using the slug with fetch_indicator. However, it does not explicitly 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.

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