Skip to main content
Glama

disease

by io.github.pipeworx-io
OverviewAdmin

Get Global Stats

get_global_stats
Read-onlyIdempotent

Check worldwide COVID-19 totals. Returns cumulative cases, deaths, recovered, active cases, plus today's new cases and deaths.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
casesYesTotal confirmed COVID-19 cases worldwide
activeYesCurrently active COVID-19 cases worldwide
deathsYesTotal confirmed COVID-19 deaths worldwide
recoveredYesTotal recovered COVID-19 cases worldwide
todayCasesYesNew COVID-19 cases reported today
todayDeathsYesNew COVID-19 deaths reported today

Schema Changelog

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

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "active": {
+      "description": "Currently active COVID-19 cases worldwide",
+      "type": "number"
+    },
+    "cases": {
+      "description": "Total confirmed COVID-19 cases worldwide",
+      "type": "number"
+    },
+    "deaths": {
+      "description": "Total confirmed COVID-19 deaths worldwide",
+      "type": "number"
+    },
+    "recovered": {
+      "description": "Total recovered COVID-19 cases worldwide",
+      "type": "number"
+    },
+    "todayCases": {
+      "description": "New COVID-19 cases reported today",
+      "type": "number"
+    },
+    "todayDeaths": {
+      "description": "New COVID-19 deaths reported today",
+      "type": "number"
+    }
+  },
+  "required": [
+    "cases",
+    "deaths",
+    "recovered",
+    "active",
+    "todayCases",
+    "todayDeaths"
+  ],
+  "type": "object"
+}
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {}
+]
  3. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, and non-destructive hints. The description adds the specific output fields returned, providing useful context about the data snapshot without contradicting the 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 sentences, front-loaded with the core purpose, and every sentence adds value. No redundant or vague wording.

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?

For a parameterless read-only tool with full annotations and an output schema, the description is complete. It explains the scope and the key returned metrics, leaving no significant gaps for an agent to select or invoke the tool.

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

Parameters4/5

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

The tool has zero parameters, and the schema already reflects this with 100% coverage. With no parameters to explain, the baseline of 4 applies; the description does not need to add parameter-level details.

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 retrieves worldwide COVID-19 totals, listing specific data categories (cumulative and daily cases, deaths, recovered, active). It distinguishes itself from siblings like get_country_stats by explicitly indicating the global scope.

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 implies the appropriate context—when worldwide aggregate COVID-19 numbers are needed—and the sibling names make alternatives apparent, though it does not explicitly state when not to use it or name alternatives.

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

All disease 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.

Resources