Skip to main content
Glama

Tsa Checkpoint Stats

tsa_checkpoint_stats
Read-onlyIdempotent

Busiest/quietest-day stats (max, min, average, total) for TSA's daily airport checkpoint screening counts over a period, e.g. "busiest travel day of 2026" or "average daily screenings last July". Pass year, a start_date/end_date range, or nothing for the current year to date. Covers 2019-01-01 through roughly yesterday's date in 2026. Returns found:false (not an error) if the period has no published data yet. Keyless.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "year": 2026
    },
    "name": "tsa_checkpoint_stats"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearNoA whole calendar year, e.g. 2024. 2019-2026.
end_dateNoRange end, YYYY-MM-DD (inclusive).
start_dateNoRange start, YYYY-MM-DD (inclusive).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / year / description
      Previous value: -"A whole calendar year, e.g. 2024. 2019-1970."New value: +"A whole calendar year, e.g. 2024. 2019-2026."
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered; the description adds context the annotations cannot: keyless access, the 2019-01-01 through roughly-yesterday coverage window, and that a missing period yields found:false rather than an error. That last point is exactly the kind of edge-case behavior an agent needs. It does not describe response shape beyond the metric list or any rate/limit behavior, so it is not a 5.

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 core capability is front-loaded in the first clause, followed by invocation options, coverage bounds, and the no-data contract. It is dense rather than padded, though the run-on first sentence packs metric list, resource and example queries together in a way that takes a second read.

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?

With zero required params and no output schema, the description carries the important burdens well: what is returned, when it is empty, what time span is legal, and that no key is needed. Only the precedence between `year` and start/end dates is missing, which is minor for a read-only reporting 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?

Schema description coverage is 100%, so the baseline is 3; the description goes beyond the schema by stating the no-parameter default (current year to date) and the overall valid data window, neither of which appears in the schema. The interaction between `year` and a date range (mutually exclusive or not) is left unstated.

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 names a specific verb class and resource: aggregate stats (max, min, average, total) over TSA daily checkpoint screening counts. The parenthetical metric list and the example questions make the returned quantity unambiguous. It does not explicitly distinguish itself from the sibling tsa_checkpoint_volumes, so it stops short of a 5.

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 gives concrete invocation patterns: pass `year`, pass a `start_date`/`end_date` range, or pass nothing for year-to-date, and illustrates the intended use with two natural-language question forms. There is no explicit 'when not to use this' or comparison to the volumes sibling, which keeps it at 4.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.