Skip to main content
Glama
Decilion

gho-mcp

by Decilion
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

country_profile

Fetch a country's latest values for curated health indicators, with optional year and indicator filters, to support comparative health systems research.

Instructions

Latest values for a curated set of headline indicators in one country.

Fetches all indicators in parallel. Within the latest year, prefers known both-sex, all-age and total-residence codes; every chosen population is labeled. Ambiguous or incomplete populations return no headline value.

Args: country: ISO3 code, country name, region code, or income-group code. year: Optional reference year. If None, returns the most recent available value per indicator. If set, returns the latest value at or before that year. indicator_codes: Optional override of the headline indicator set. Defaults to a curated comparative-health-systems list. indicator_dim_filters: Per-indicator dimension filters, e.g. {"SDGPM25": {"Dim1": "RESIDENCEAREATYPE_TOTL"}}. Keys use the same whitelist as get_indicator_data. Filters apply before latest year selection; unmatched indicator keys raise an error.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
yearNo
countryYes
indicator_codesNo
indicator_dim_filtersNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.7.0
    • addedInput schema / properties / indicator_dim_filters
      Added value: +{
+  "anyOf": [
+    {
+      "additionalProperties": {
+        "additionalProperties": {
+          "type": "string"
+        },
+        "type": "object"
+      },
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Indicator Dim Filters"
+}
  2. First observedv0.6.1

TDQS

A4.5/5.0
Behavior5/5

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

With zero annotations, the description carries the full burden and does so thoroughly: it discloses parallel fetching, the preference for both-sex/all-age/total-residence codes, labeling of populations, the no-value behavior for ambiguous populations, the year-selection semantics, and the error behavior for unmatched filter keys.

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 purpose is front-loaded in one clear sentence and the Args section is organized. It is on the longer side, but nearly every clause carries semantic weight — defaults, ordering, error behavior — so little is waste.

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 a rich output schema, the description appropriately omits return-format details while covering defaults, parameter semantics, error conditions, and selection behavior. No critical gap remains for an agent to call this correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, and the description fully compensates: it defines valid country inputs (ISO3, name, region, income-group), explains year semantics including the None default, describes the indicator_codes override with its default curated list, and gives a concrete example for indicator_dim_filters plus ordering and error rules.

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 first sentence states a specific verb ('returns latest values'), a specific resource ('headline indicators'), and a scope ('in one country'). This distinguishes it from siblings like compare_countries and get_indicator_data without needing to open their schemas.

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 when to use it — a country-level snapshot of a curated indicator set — and references get_indicator_data's whitelist for filter keys, which helps route an agent. However, it never explicitly states when NOT to use it or names an alternative for cases like raw data pulls or cross-country comparison.

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