disease

Get Country Stats

get_country_stats

Read-onlyIdempotent

Check COVID-19 stats for a specific country (e.g., "US", "India", "GB"). Returns cases, deaths, recovered, active cases, today's change, and population.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`country`	Yes	Country name or ISO code (e.g., "USA", "germany", "gb")

Output Schema

TableJSON Schema

Name	Required	Description
`cases`	Yes	Total confirmed COVID-19 cases in country
`active`	Yes	Currently active COVID-19 cases in country
`deaths`	Yes	Total confirmed COVID-19 deaths in country
`country`	Yes	Country name
`recovered`	Yes	Total recovered COVID-19 cases in country
`population`	Yes	Total population of country
`todayCases`	Yes	New COVID-19 cases reported today in country
`todayDeaths`	Yes	New COVID-19 deaths reported today in country

Schema Changelog

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

Changed1 schema field changedMay 8, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "active": {
+      "description": "Currently active COVID-19 cases in country",
+      "type": "number"
+    },
+    "cases": {
+      "description": "Total confirmed COVID-19 cases in country",
+      "type": "number"
+    },
+    "country": {
+      "description": "Country name",
+      "type": "string"
+    },
+    "deaths": {
+      "description": "Total confirmed COVID-19 deaths in country",
+      "type": "number"
+    },
+    "population": {
+      "description": "Total population of country",
+      "type": "number"
+    },
+    "recovered": {
+      "description": "Total recovered COVID-19 cases in country",
+      "type": "number"
+    },
+    "todayCases": {
+      "description": "New COVID-19 cases reported today in country",
+      "type": "number"
+    },
+    "todayDeaths": {
+      "description": "New COVID-19 deaths reported today in country",
+      "type": "number"
+    }
+  },
+  "required": [
+    "country",
+    "cases",
+    "deaths",
+    "recovered",
+    "active",
+    "todayCases",
+    "todayDeaths",
+    "population"
+  ],
+  "type": "object"
+}

Changed1 schema field changedMay 6, 2026

addedInput schema / examples

Added value: +[
+  {
+    "country": "US"
+  },
+  {
+    "country": "india"
+  }
+]

First observedApr 14, 2026

TDQS

A4.1/5.0

Behavior3/5

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

Annotations already declare the tool safe (readOnlyHint, idempotentHint, destructiveHint). The description adds the list of returned fields (cases, deaths, etc.), but this is likely already in the output schema. It also gives example country codes, which is useful but not deeply behavioral. No additional traits like data freshness or rate limits are disclosed, so with annotations covering safety, a 3 is appropriate.

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 a single sentence that front-loads the purpose, provides illustrative examples, and lists the return fields. Every word earns its place, with no redundancy or filler.

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?

The tool is simple with one parameter, a clear purpose, and an output schema exists. The description is complete enough for an agent to select and invoke the tool correctly, including examples and the type of data returned. No critical information is missing.

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% and the single parameter 'country' is well described as 'Country name or ISO code'. The description reinforces this with examples (US, India, GB) but does not add significant new semantics beyond the schema. Baseline 3 is correct.

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 tool's purpose: 'Check COVID-19 stats for a specific country'. It uses a specific verb ('check') and resource ('COVID-19 stats'), and the scope is defined by 'specific country'. The return list further clarifies the tool's function, and the example country codes distinguish it from sibling tools like get_global_stats or get_historical.

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 clearly implies when to use the tool: when you need current COVID-19 stats for a single country. It does not explicitly mention alternatives or exclusions, but the context 'for a specific country' differentiates it from global or historical tools. This is a clear context without explicit when-not guidance, so a 4 is appropriate.

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

All disease tools Inspect

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.