Skip to main content
Glama

Refresh Cache

refresh_cache

Clears cached API responses so subsequent queries re-fetch health data; specify a cache namespace or clear all enabled sources.

Instructions

Clear cached API responses. The next query re-fetches.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

NameRequiredDescriptionDefault
sourceNoCache namespace to clear: 'all' or an enabled source name. get_status lists the enabled sources.all

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden; it does disclose the key consequence that data is re-fetched on the next query, implying the clear is recoverable rather than destructive. It says nothing about in-flight requests, whether clearing affects other clients, or cost of the subsequent re-fetch.

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, front-loaded with the action and followed by the consequence. No filler or redundant restatement of the title.

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 one-optional-parameter tool with a full schema and an output schema, the description covers the action and its effect adequately. A brief note on scope (whole cache vs one source) or on concurrency would make it fully complete.

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% and the single source parameter already documents the 'all' default and points at get_status for enabled sources. The description adds no further meaning about the parameter, so baseline 3 applies.

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?

States a specific verb and resource: 'Clear cached API responses,' which is unambiguous and distinguishable from the read-only get_* siblings. It stops short of explicitly naming when a sibling is preferable, so it is clear but not differentiated in so many words.

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?

Usage is only implied through 'The next query re-fetches,' which hints at using this when cached data is stale. There is no explicit when-to-use, when-not-to-use, or pointer to an alternative action.

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