Skip to main content
Glama

Refresh cache dashboard

refresh_cache_dashboard
Read-only

Refresh the Gauge dashboard for the current chat without a model call to view updated local token and cache usage.

Instructions

Refresh Gauge for the current chat without a model call.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "session_id": "<session_id>"
    },
    "name": "refresh_cache_dashboard"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
session_idYesThe current chat ID. Never substitute another chat.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description does add one real piece of behavior beyond them - no model call is incurred - which tells the agent this is a cheap operation. It says nothing about what is re-read, whether cached values are replaced, or how freshness is determined.

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?

A single front-loaded sentence with no filler; the scope ('current chat') and the key differentiator ('without a model call') arrive immediately. Brevity here costs it coverage, but no sentence is wasted.

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

Completeness3/5

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

For a two-parameter read-only tool with no output schema, the definition is callable but thin: it never explains what 'Gauge' returns or what limit bounds, and an agent cannot predict the response shape. Adequate for invocation, incomplete for understanding the effect.

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

Parameters2/5

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

The description reinforces session_id only obliquely ('the current chat'), which the schema already spells out as 'The current chat ID. Never substitute another chat.' The second parameter, limit (default 500, max 2000), has no schema description and no mention in the description, leaving its meaning entirely to guesswork.

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 ('Refresh') and resource ('Gauge') scoped to 'the current chat', and adds a distinguishing property ('without a model call') that separates it from a plain render like show_cache_dashboard. It stops short of naming that sibling explicitly, so the differentiation is implicit rather than stated.

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?

The phrase 'without a model call' implies when this is preferable (a cheap, non-inference refresh of the existing gauge), but the description never says when to use this instead of show_cache_dashboard or get_cache_summary, and gives no preconditions or exclusions. Guidance is inferable, not stated.

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