Skip to main content
Glama

jp_lit_search_cache_index

Read-onlyIdempotent

Search across saved jp_lit_search cache entries and retrieve cache keys for re-extraction or export. Filter by query, source, date, or session.

Instructions

read-only。保存済み jp_lit_search cache を横断検索し、再抽出や export に渡せる cache_key 一覧を返す。新規に外部検索したい場合は jp_lit_search、保存済み cache の棚卸しは jp_lit_list_cache、検索結果の集合演算や重複確認は jp_lit_refine_results を使う。ローカル cache と session 紐づけを読むだけで、cache や session は変更しない

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo返す cache entry の最大件数。最大 200。
queryYes保存済み jp_lit_search 結果内で探す語。元の検索語、タイトル、著者、件名、source_id を NFKC 正規化して部分一致検索する。
sourceNo保存済み検索結果の source を絞る。例: ndl_catalog, cinii_books。未指定なら source を問わない。
saved_onNocache 保存日の簡易指定。YYYY-MM-DD, today, yesterday, last_7_days のいずれか。
saved_toNocache saved_at の上限 ISO datetime。saved_from と組み合わせて保存時刻を絞る。
issued_toNo結果 item の issued_at 上限。issued_from と組み合わせて刊行年範囲を絞る。
saved_fromNocache saved_at の下限 ISO datetime。saved_on より細かく保存時刻を絞る場合に使う。
session_idNoこのセッションに紐づく jp_lit_search cache だけを検索する。未指定なら全セッションに紐づく cache を対象にする。
issued_fromNo結果 item の issued_at 下限。年だけの '1900' など、既存データと同じ文字列表現で比較する。

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
itemsYes
limitYes
queryYes
totalYes
sourceYes
saved_onYes
saved_toYes
issued_toYes
cache_keysYes
saved_fromYes
session_idYes
issued_fromYes
saved_on_resolvedYes
Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint. Description adds that it only reads local cache and session bindings, does not modify cache or sessions, reinforcing the read-only nature without contradiction.

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?

Description is concise with three sentences: first states read-only purpose, second gives alternatives, third clarifies behavior. No unnecessary words.

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 fully documented in schema, presence of output schema, and clear annotation coverage, the description sufficiently completes the picture. It explains what the tool returns and its behavior.

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 baseline 3 is appropriate. The description does not add additional parameter meaning beyond what the schema already provides, but it does not need to due to full coverage.

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 it is read-only, searches across saved jp_lit_search cache, and returns a list of cache_keys for re-extraction or export. It distinguishes from sibling tools like jp_lit_search, jp_lit_list_cache, and jp_lit_refine_results.

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 tells when to use this tool vs alternatives: for searching existing cache, use this; for new external search, use jp_lit_search; for cache inventory, use jp_lit_list_cache; for set operations, use jp_lit_refine_results.

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