ghed-mcp

Overview Schema Source Related Servers Discussions Admin

compare_trends

Read-only

Compare multiple health expenditure indicators across countries, regions, or income groups by computing first/latest summaries, percent change, CAGR, and absolute share changes.

Instructions

Compute first/latest summaries for several indicators; use indicator_trend for one.

percent_change and cagr are fractions (0.10 = 10%); absolute changes in shares are percentage points. Check each item's years, warnings and limits.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`income`	No
`region`	No
`year_end`	No
`countries`	No
`year_start`	No
`country_group`	No
`min_year_count`	No
`indicator_codes`	Yes
`min_period_years`	No
`top_per_indicator`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.6.1Sep 22, 2026

addedInput schema / properties / min_period_years

Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Min Period Years"
+}

addedInput schema / properties / min_year_count

Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Min Year Count"
+}

First observedv0.5.1Jun 4, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Beyond the read-only and open-world annotations, the description adds important output semantics: percent_change and cagr are fractions, absolute share changes are percentage points, and the agent should inspect years, warnings, and limits. This helps the agent correctly interpret results and anticipate caveats.

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 compact and front-loaded; the main action is stated first, followed by crucial numeric interpretation notes and a caveat. Every sentence carries useful information, though some phrasing (e.g., 'first/latest summaries') is slightly terse.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 10 parameters, zero schema descriptions, and no parameter-level guidance in the prose, the description is not complete enough for an agent to confidently set filters and thresholds. The output schema exists and the numeric caveats help, but input semantics remain largely undocumented.

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

Parameters1/5

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

Schema description coverage is 0% and the description does not explain any of the 10 parameters. It references indicators and output metrics, but nothing about country/region filters, year ranges, min_year_count, min_period_years, or top_per_indicator. The description fails to compensate for the complete lack of schema-level parameter documentation.

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 states a specific operation ('Compute first/latest summaries') on a specific resource ('several indicators') and explicitly contrasts itself with indicator_trend for a single indicator. This makes its scope clear and distinguishes it from a key sibling tool.

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?

It explicitly tells the agent to use indicator_trend when only one indicator is needed, giving a clear routing rule. It does not discuss other siblings like compare_countries or compare_country_group, but the single-vs-several indicator distinction provides clear enough context for the main alternative.

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