Skip to main content
Glama

reference_refresh

Read-only

Clear cached project-membership data so the next reference query re-reads Visual Studio and returns current results.

Instructions

Drop the cached project-membership data so the next reference query reads Visual Studio again.

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": "reference_refresh"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
okYes
errorNo
freshnessYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.16.0

TDQS

A3.7/5.0
Behavior3/5

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

The description adds real context beyond the annotations by clarifying the scope of what is discarded (only cached project-membership data, not source or project files) and that the refresh is lazy, occurring on the next reference query. However, 'Drop' sits in mild tension with readOnlyHint=true, and the description does not address whether the cache is rebuilt automatically or what happens to in-flight queries.

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?

A single sentence with zero waste: the action comes first and the downstream effect follows immediately. Nothing is redundant or padded.

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 zero-parameter cache-invalidation tool with an output schema available, the description covers the action and its effect adequately. The only missing element is any operational note about cost or frequency of use, which is minor given the tool's simplicity.

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?

The tool takes no parameters, so the baseline is 4. The description correctly implies there is nothing to target or scope — the entire project-membership cache is dropped — which is consistent with the empty input schema.

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 ('Drop the cached project-membership data') plus the consequence ('next reference query reads Visual Studio again'). This clearly distinguishes it from read-style siblings like reference_references or reference_tree, though it never names an alternative such as reference_reindex, which could plausibly overlap.

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 implied rather than stated: the agent can infer it should call this when cached membership data is stale and fresh reads from Visual Studio are needed. There is no explicit 'call this before X' or 'do not call this when Y', and no mention of the related reference_reindex sibling that an agent might confuse it with.

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