Skip to main content
Glama
lzinga

US Government Open Data MCP

by lzinga
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

clear_cache

DestructiveIdempotent

Remove cached API responses to force fresh data on next query. Specify a data source to clear only that cache, or omit to clear all.

Instructions

Clear cached API responses to force fresh data on next query. Specify a source name or omit to clear all.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sourceNoModule name to clear: bea, bls, bts, cdc, census, cfpb, clinical-trials, cms, college-scorecard, congress, doj-news, dol, eia, epa, epa-aqs, fbi, fda, fdic, fec, federal-register, fema, fred, govinfo, gsa-calc, hud, naep, nhtsa, nih, noaa, nrel, nws, open-payments, regulations, sec, senate-lobbying, treasury, usaspending, usda-fooddata, usda-nass, usgs, uspto, world-bank. Omit for all.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2026.9.14
    • changedInput schema / properties / source / description
      Previous value: -"Module name to clear: bea, bls, bts, cdc, census, cfpb, clinical-trials, cms, college-scorecard, congress, doj-news, dol, eia, epa, epa-aqs, fbi, fda, fdic, fec, federal-register, fema, fred, govinfo, gsa-calc, hud, naep, nhtsa, nih, noaa, nrel, open-payments, regulations, sec, senate-lobbying, treasury, usaspending, usda-fooddata, usda-nass, usgs, uspto, world-bank. Omit for all."New value: +"Module name to clear: bea, bls, bts, cdc, census, cfpb, clinical-trials, cms, college-scorecard, congress, doj-news, dol, eia, epa, epa-aqs, fbi, fda, fdic, fec, federal-register, fema, fred, govinfo, gsa-calc, hud, naep, nhtsa, nih, noaa, nrel, nws, open-payments, regulations, sec, senate-lobbying, treasury, usaspending, usda-fooddata, usda-nass, usgs, uspto, world-bank. Omit for all."
  2. Changed1 schema field changedv2026.4.11
    • removedInput schema / additionalProperties
      Removed value: -false
  3. First observedv2026.3.9

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true. The description adds the behavioral effect (forces fresh data on next query) and clarifies the scope of clearing (all or specific source), which complements the annotations without contradicting them.

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, front-loaded sentence that states the purpose and parameter behavior with zero fluff. Every word contributes value.

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?

For a simple tool with one optional parameter, annotations covering destructiveness and idempotency, and a fully documented schema, the description provides enough context. It doesn't describe the return value, but no output schema exists and it's not essential for a cache-clearing operation.

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% – the parameter description already lists all valid source values and states that omitting clears all. The tool description adds no new meaning beyond what the schema provides, so the baseline of 3 applies.

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 states a specific verb (Clear) and resource (cached API responses) with a clear goal (force fresh data on next query). It is distinct from all sibling tools, which are data-fetching operations, making this unique and unambiguous.

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 explains when to use it (to force fresh data) and how to scope it (specify a source or omit for all). It does not explicitly discuss alternatives because none exist; the usage context is clear and actionable.

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

Deploy Server

Other Tools