Skip to main content
Glama

cache

Search previously cached web content instantly using full-text search, URL patterns, and date filters to avoid network requests.

Instructions

Search previously fetched content without hitting the network. Run this BEFORE any search/fetch — cache hits return instantly with full markdown.

Key parameters:

  • query: FTS5 full-text search over cached markdown + titles (supports AND, OR, NOT, "phrase").

  • url_pattern: glob filter on URLs (e.g. "example.com").

  • since: ISO date — only entries cached after this date.

  • stats: true to get cache size, entry count, oldest/newest dates.

  • clear: true to delete matching entries.

Persists across sessions. No remote round-trip.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeNoSearch strategy when query is provided. "fts" (default) runs keyword-only BM25 over the FTS5 index. "hybrid" additionally runs semantic vector search and fuses both rankings with reciprocal rank fusion for higher-recall lookups; falls back to FTS when the embedding index is empty or unavailable.
clearNoClear matching cache entries (requires at least one filter: query, url_pattern, or since)
limitNoMaximum number of results to return (default 20).
queryNoFull-text search over cached content
sinceNoISO date — only results cached after this date
statsNoReturn cache statistics (total URLs, size, date range)
url_patternNoFilter by URL glob pattern (e.g., "*example.com*")
check_changesNoRe-fetch all matching cached URLs and report which ones have changed. Returns a list of URLs with changed/unchanged status and diff summaries. Use with query or url_pattern to scope which cached entries to check.
max_tokens_outNoToken-budget cap on total output (cl100k-base BPE). Caps the aggregate size of all returned markdown bodies; bodies past the budget are truncated or dropped.
Behavior5/5

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

With no annotations, the description fully discloses behavior: no network round-trip, persistence across sessions, FTS5 search capabilities, support for globs, date filtering, stats, and clear. It also explains the mode parameter's fallback strategy and the check_changes feature. No gaps or contradictions.

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 front-loaded with purpose and guidance, then uses a bullet list for key parameters, and ends with a summary line. Every sentence provides essential information without redundancy. Efficient and well-organized.

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

Completeness5/5

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

Given 9 parameters with no output schema, the description covers all behaviors including complex ones like hybrid search and change detection. It sufficiently equips an agent to use the tool correctly without ambiguity.

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

Parameters5/5

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

Schema coverage is 100%, yet the description adds significant value: it details FTS5 operators for query, explains hybrid vs fts mode, requires filters for clear, describes stats output, and elaborates on check_changes. This greatly aids correct usage.

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 clearly states the tool's purpose: 'Search previously fetched content without hitting the network.' It specifies the verb (search) and resource (cached content), and distinguishes itself from sibling tools like fetch and search by directing the user to run this before them.

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 explicitly instructs to 'Run this BEFORE any search/fetch' and implies it's for instant cache hits. While it doesn't explicitly list alternatives for cache misses, the context is clear enough. Lacks explicit 'when not to use' but still provides strong guidance.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/KnockOutEZ/wigolo'

If you have feedback or need assistance with the MCP directory API, please join our Discord server