Skip to main content
Glama

jp_lit_resolve_authority

Look up authority records for persons, corporate bodies, subjects, and uniform titles from Web NDL Authorities to confirm identities and find safe search terms.

Instructions

external read / local bookkeeping write(非破壊)。Web NDL Authorities で人名・団体名・件名などの典拠候補を確認し、別名義や安全な検索ヒントを返す。文献検索 source ではなく検索語展開・名義確認の補助 tool。分類記号から件名候補を探す場合は jp_lit_find_authority_terms_by_classification、実際の文献検索は jp_lit_search を使う 外部sourceは変更しない。cache hitでもlocal session履歴を更新し、cache missまたはforce_refreshではlocal cacheを作成・置換する。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeNo探す典拠種別。all は人名・団体名・件名などを横断する。all
limitNo返す典拠候補の最大件数。最大 20。
queryYes確認したい人名・団体名・件名・統一タイトルなどの典拠検索語。
force_refreshNotrue の場合はローカル cache を使わず upstream API から再取得する。false の場合は保存済み cache を優先する。

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeYes
cacheNo
itemsYes
limitYes
queryYes
totalYes
search_hintsYes
Behavior5/5

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

The description explains that the tool performs external reads and local bookkeeping writes without destructiveness. It details cache hit/miss behavior and session history updates. These details add value beyond annotations, which list readOnlyHint=false but do not specify the nature of local writes.

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 fairly concise with two main sentences covering purpose and usage guidance. It is front-loaded with the core function. Some additional details on caching could be omitted but are helpful for understanding side effects.

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 the complexity of the tool (external API, caching, session updates), the description covers purpose, usage context, behavioral effects, and distinguishes siblings. An output schema exists, so return values are documented elsewhere.

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% with each parameter having a description. The tool description does not add additional meaning beyond what is already in the schema. Baseline score of 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?

The description clearly states the tool's purpose: to confirm authority candidates (names, subjects, etc.) from Web NDL Authorities and return alternative names/safe search hints. It distinguishes itself from literature search tools and sibling tools like jp_lit_find_authority_terms_by_classification and jp_lit_search.

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 explicitly tells when to use this tool (for search term expansion and name confirmation) and when not (not a literature search source). It also provides alternatives for classification-based searches and actual literature searches.

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