Skip to main content
Glama

jp_lit_search_cache_index

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

Output Schema

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

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

No annotations are provided, so the description carries the full burden. It explicitly states 'read-only' and 'does not modify cache or session', which is a key behavioral trait for a search/index tool. While it does not cover rate limits or response size, the core safety aspect is communicated.

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 well-structured and front-loaded with 'read-only' and the core purpose. It efficiently lists alternatives in a second sentence and ends with a safety note. The length is appropriate given the complexity, and every sentence adds value.

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 9 parameters, an output schema, and no nested objects, the tool description provides sufficient context: it explains the purpose, scope, and key constraints (read-only, session binding). The return type (cache_key list) is implied. The output schema presumably covers return values, so the description is complete enough.

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 description coverage is 100%, so the baseline is 3. The tool description does not add significant new meaning beyond the schema; it reiterates that query searches across fields, but that is already in the schema. No additional parameter semantics are provided.

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 a read-only tool that searches across saved jp_lit_search caches and returns cache keys. It explicitly distinguishes itself from sibling tools like jp_lit_search (new external search), jp_lit_list_cache (inventory), and jp_lit_refine_results (set operations).

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?

The description provides explicit when-to-use and when-not-to-use guidance, naming alternative tools for different tasks: jp_lit_search for new searches, jp_lit_list_cache for inventory, and jp_lit_refine_results for set operations. This helps the agent select the correct tool.

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