disease

Get Historical

get_historical

Read-onlyIdempotent

Get daily COVID-19 timeline for a country or globally. Returns historical progression of cases, deaths, and recoveries by date.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`days`	No	Number of days of history to return (default: 30)
`country`	No	Country name or "all" for global data (default: "all")

Output Schema

TableJSON Schema

Name	Required	Description
`days`	Yes	Number of days of history returned
`country`	Yes	Country name or 'all' for global data
`timeline`	Yes

Schema Changelog

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

Changed2 schema fields changedMay 24, 2026

addedInput schema / examples

Added value: +[
+  {
+    "country": "all",
+    "days": 30
+  },
+  {
+    "country": "GB",
+    "days": 90
+  }
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "country": {
+      "description": "Country name or 'all' for global data",
+      "type": "string"
+    },
+    "days": {
+      "description": "Number of days of history returned",
+      "type": "number"
+    },
+    "timeline": {
+      "properties": {
+        "cases": {
+          "additionalProperties": {
+            "type": "number"
+          },
+          "description": "Daily case counts by date (YYYY/M/D format)",
+          "type": "object"
+        },
+        "deaths": {
+          "additionalProperties": {
+            "type": "number"
+          },
+          "description": "Daily death counts by date (YYYY/M/D format)",
+          "type": "object"
+        },
+        "recovered": {
+          "additionalProperties": {
+            "type": "number"
+          },
+          "description": "Daily recovery counts by date (YYYY/M/D format)",
+          "type": "object"
+        }
+      },
+      "required": [
+        "cases",
+        "deaths",
+        "recovered"
+      ],
+      "type": "object"
+    }
+  },
+  "required": [
+    "country",
+    "days",
+    "timeline"
+  ],
+  "type": "object"
+}

Changed2 schema fields changedMay 13, 2026

removedInput schema / examples

Removed value: -[
-  {
-    "_apiKey": "your-metals-api-key",
-    "date": "2024-01-15"
-  },
-  {
-    "_apiKey": "your-metals-api-key",
-    "base": "GBP",
-    "date": "2023-06-30",
-    "symbols": "XAU,XCU"
-  }
-]

changedOutput schema / (root)

Previous value: -{
-  "properties": {
-    "base": {
-      "description": "Base currency code (e.g., USD, EUR)",
-      "type": "string"
-    },
-    "date": {
-      "description": "Historical date in YYYY-MM-DD format",
-      "type": "string"
-    },
-    "rates": {
-      "additionalProperties": {
-        "type": "number"
-      },
-      "description": "Metal spot prices per troy ounce, keyed by symbol (e.g., XAU, XAG)",
-      "type": "object"
-    },
-    "timestamp": {
-      "description": "Unix timestamp of when prices were captured",
-      "type": "number"
-    }
-  },
-  "required": [
-    "base",
-    "date",
-    "timestamp",
-    "rates"
-  ],
-  "type": "object"
-}New value: +null

Changed1 schema field changedMay 8, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "base": {
+      "description": "Base currency code (e.g., USD, EUR)",
+      "type": "string"
+    },
+    "date": {
+      "description": "Historical date in YYYY-MM-DD format",
+      "type": "string"
+    },
+    "rates": {
+      "additionalProperties": {
+        "type": "number"
+      },
+      "description": "Metal spot prices per troy ounce, keyed by symbol (e.g., XAU, XAG)",
+      "type": "object"
+    },
+    "timestamp": {
+      "description": "Unix timestamp of when prices were captured",
+      "type": "number"
+    }
+  },
+  "required": [
+    "base",
+    "date",
+    "timestamp",
+    "rates"
+  ],
+  "type": "object"
+}

Changed1 schema field changedMay 6, 2026

addedInput schema / examples

Added value: +[
+  {
+    "_apiKey": "your-metals-api-key",
+    "date": "2024-01-15"
+  },
+  {
+    "_apiKey": "your-metals-api-key",
+    "base": "GBP",
+    "date": "2023-06-30",
+    "symbols": "XAU,XCU"
+  }
+]

First observedApr 14, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, indicating a safe read operation. The description adds value by specifying that it returns 'historical progression of cases, deaths, and recoveries by date,' which clarifies the temporal nature of the data 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?

The description is concise, consisting of two sentences that immediately state the purpose and return content. Every word adds value 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 only two optional parameters. The description, combined with the rich annotations and the presence of an output schema, provides sufficient context for an agent to understand what the tool does and what it returns. No additional information seems necessary.

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?

Both parameters (days and country) have descriptions in the schema, providing full coverage. The description's mention of 'for a country or globally' and 'daily' aligns with the schema but does not add significant additional meaning beyond what is already in the parameter descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's function: 'Get daily COVID-19 timeline for a country or globally' with specific mention of cases, deaths, and recoveries. This distinguishes it from sibling tools like get_country_stats and get_global_stats, which likely focus on current statistics rather than historical progression, but it does not explicitly name those alternatives.

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 usage for historical timeline queries but does not explicitly state when to use this tool versus alternatives such as get_global_stats or get_vaccine_stats. It lacks explicit when/when-not guidance, so the agent must infer the use case from the word 'historical.'

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.

Get Historical

Input Schema

Output Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources