Skip to main content
Glama

disease

by io.github.pipeworx-io
OverviewAdmin

Get Vaccine Stats

get_vaccine_stats
Read-onlyIdempotent

Check COVID-19 vaccination progress for a country or globally. Returns cumulative doses administered daily over the past 30 days.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
countryNoCountry name to get vaccine data for. Omit for global totals.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
countryYesCountry name or 'global' for worldwide data
timelineYesDaily cumulative vaccine doses administered by date

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": {
+    "country": {
+      "description": "Country name or 'global' for worldwide data",
+      "type": "string"
+    },
+    "timeline": {
+      "additionalProperties": {
+        "type": "number"
+      },
+      "description": "Daily cumulative vaccine doses administered by date",
+      "type": "object"
+    }
+  },
+  "required": [
+    "country",
+    "timeline"
+  ],
+  "type": "object"
+}
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "country": "USA"
+  },
+  {}
+]
  3. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already mark it as read-only, idempotent, and non-destructive. The description adds behavioral context by specifying the return granularity (daily cumulative doses) and the 30-day window. No contradictions or further disclosures needed.

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?

Two short sentences fully communicate purpose and scope with no redundant information. Front-loaded with the main action.

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

Completeness4/5

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

Given the single optional parameter, rich annotations, and existence of an output schema (per context signals), the description covers the essential context: what it does, the scope, and time range. It lacks only explicit guidance on alternatives, but that's not critical for a simple read tool.

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?

The schema provides 100% coverage with a clear description of the country parameter and the omission behavior. The description's mention of 'country or globally' mirrors the schema without adding new semantic detail, so baseline 3 is appropriate.

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 it checks COVID-19 vaccination progress and specifies the return data (cumulative doses administered daily over past 30 days), which distinguishes it from general stats tools. However, it doesn't explicitly differentiate from sibling tools like get_country_stats or get_global_stats.

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?

It implies usage for vaccine-related queries by mentioning 'COVID-19 vaccination progress' and 'country or globally,' but provides no explicit exclusions or references to alternatives when historical or other stats are needed.

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