Skip to main content
Glama

jp_lit_list_cache

Read-onlyIdempotent

List and filter local caches from Japanese literature searches by tool, session, or date to find specific cache keys for review or deletion.

Instructions

read-only。ローカル cache の一覧・集計を返し、tool、session_id、保存日、source で絞り込める。cache_key を探す棚卸しに使う。保存済み jp_lit_search の中身を語で横断検索したい場合は jp_lit_search_cache_index、削除は jp_lit_delete_cache または jp_lit_prune_cache を使う。cache や session は変更しない

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toolNo一覧対象の tool cache 名。未指定なら全 tool cache を対象にする。
limitNo返す cache entry の最大件数。最大 500。
sourceNo保存済み検索結果の source で絞る。source を持たない cache には一致しない。
saved_onNocache 保存日の簡易指定。YYYY-MM-DD, today, yesterday, last_7_days のいずれか。
saved_toNocache saved_at の上限 ISO datetime。
saved_fromNocache saved_at の下限 ISO datetime。
session_idNoこのセッションに紐づく cache だけを一覧する。

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
toolYes
itemsYes
limitYes
totalYes
sourceYes
summaryYes
saved_onYes
saved_toYes
cache_keysYes
saved_fromYes
session_idYes
saved_on_resolvedYes
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false. The description adds 'read-only' and 'cache/session unchanged', which is consistent and provides a bit more context but the annotations carry the main burden.

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?

The description is concise (several sentences) and front-loaded with purpose. Every sentence adds value, though it could be slightly more structured for easier scanning.

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?

Given the presence of an output schema and full parameter documentation in the schema, the description is complete enough. It states the return type (list/aggregation) and filter criteria, which is sufficient for an agent to decide on usage.

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% so the schema already documents all parameters. The description mentions the filter capabilities but does not add new meaning beyond the schema's descriptions. Baseline 3 is appropriate.

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?

Description clearly states it returns a list/summary of local cache with filtering by tool, session_id, saved_on, source. It distinguishes from siblings like jp_lit_search_cache_index (for cross-word search) and jp_lit_delete_cache/jp_lit_prune_cache (for deletion).

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 it is used for inventory to find cache_key, and directs the agent to alternative tools for different tasks (cross-search, deletion). Also notes it does not modify cache or sessions.

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