Skip to main content
Glama

jp_lit_refine_results

Locally sort, filter, and apply set operations on cached Japanese literature search results, with optional duplicate cluster detection, avoiding upstream re-search.

Instructions

保存済み jp_lit_search 結果を upstream 再検索せずローカルでソート・フィルタ・集合演算し、必要時だけ重複候補クラスタも返す

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cache_keyNo
cache_keysNo
session_idNo
combineNounion
key_byNosource_record
sort_byNo
sort_orderNoasc
limitNo
offsetNo
include_duplicate_clustersNo
cluster_limitNo
cluster_offsetNo
cluster_member_limitNo
filtersNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
base_cache_keyYes
base_cache_keysYes
combineYes
key_byYes
totals_by_baseYes
total_beforeYes
total_afterYes
limitYes
offsetYes
itemsYes
cluster_summaryNo
clustersNo
Behavior3/5

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

No annotations provided; description adds key behavioral context (local operation, no upstream calls, optional duplicate clusters) but does not disclose side effects, auth requirements, or exact return behavior.

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?

Single sentence conveys essential purpose and key constraints without redundancy; front-loaded and efficient.

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

Completeness2/5

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

Despite high complexity (14 parameters, nested objects, output schema), the description provides only a high-level summary, omitting parameter interactions, defaults, and filter structure necessary for correct invocation.

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

Parameters2/5

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

Schema description coverage is 0% for 14 parameters; description only mentions high-level operations (sort, filter, set) without explaining individual parameters like cache_key, filters, or cluster options, leaving the agent underinformed.

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 the tool refines saved search results locally without upstream re-search, specifying sorting, filtering, set operations, and optional duplicate clusters. It distinguishes from sibling search/retrieval tools.

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

Usage Guidelines3/5

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

Implicitly indicates use for refining saved results, but lacks explicit when-to-use or when-not-to-use guidance and alternative siblings are not named.

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