Skip to main content
Glama

jp_lit_prune_cache

Remove old cached search results from Japanese literature databases. Preview candidates with dry run, then delete outdated cache entries to free space.

Instructions

delete when dry_run=false。古いローカル cache 候補を列挙し、既定の dry_run=true では削除せず候補だけ返す。dry_run=false のときだけ older_than_days と limit に一致する cache を削除する。個別 cache_key を削除する場合は jp_lit_delete_cache、一覧確認だけなら jp_lit_list_cache を使う

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
older_than_daysNoこの日数より古い cache を prune 候補にする。
toolNo対象 tool cache 名。未指定なら全 tool cache を対象にする。
dry_runNotrue なら削除せず候補だけ返す。false のときだけ実際に古い cache を削除する。
limitNo列挙または削除する候補の最大件数。最大 1000。

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dry_runYes
older_than_daysYes
cutoff_saved_atYes
toolYes
limitYes
matched_countYes
pruned_countYes
total_bytesYes
candidatesYes
skipped_countYes
skippedYes
messageYes
Behavior4/5

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

Discloses dry_run default (true) prevents deletion, and only false triggers deletion based on older_than_days and limit. No annotations provided, so description carries full burden. It could mention reversibility or side effects, but major behaviors are clear.

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 sentences in Japanese, front-loaded with core action. No wasted words. Every sentence adds value.

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?

Complete given output schema exists. Parameters well documented, siblings differentiated, behavior under dry_run explained. No missing context for a cache pruning tool.

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?

Schema coverage is 100%. The description adds practical context: dry_run=false triggers deletion, and deletion uses older_than_days and limit. Ties parameters to the tool's behavior beyond schema descriptions.

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 deletes old cache when dry_run=false and lists candidates otherwise. It specifies criteria (older_than_days, limit) and distinguishes from siblings jp_lit_delete_cache and jp_lit_list_cache.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states when to use: for bulk deletion or listing candidates. Provides alternatives: jp_lit_delete_cache for individual cache_key deletion, jp_lit_list_cache for listing only.

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/itarunnn/jp-lit-mcp'

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