Skip to main content
Glama

jp_lit_suggest_classification_codes

Converts a subject term into NDC/NDLC classification codes from Web NDL Authorities, returning a suggested category parameter for CiNii Books searches.

Instructions

read-only。Web NDL Authorities で件名語から NDC/NDLC 分類記号を探し、CiNii Books の category filter に渡せる suggested_category_param と jp_lit_search 呼び出し例を返す。分類記号から件名語を探す場合は jp_lit_find_authority_terms_by_classification、実際の文献検索は jp_lit_search を使う

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
termYes分類記号を探す元になる件名・主題語。例: 近代日本文学。
schemesNo返す分類体系。CiNii Books category には NDC/NDLC の notation を半角スペース区切りで渡す。
max_codesNosuggested_category_param に含める分類記号の最大件数。
concept_limitNoNDLSH 件名概念候補の最大件数。
force_refreshNotrue の場合はローカル cache を使わず upstream API から再取得する。false の場合は保存済み cache を優先する。

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
termYes
cacheNo
itemsYes
cautionYes
schemesYes
max_codesYes
used_codesYes
total_codesYes
concept_limitYes
total_conceptsYes
suggested_searchYes
suggested_category_paramYes
Behavior3/5

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

With no annotations provided, the description carries the full burden. It declares the tool is read-only, which is positive, but does not disclose caching behavior, rate limits, or what happens when no results are found. The force_refresh parameter hints at caching, but the description itself lacks explicit behavioral details.

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?

The description is two sentences, front-loads the core function, and provides cross-references to related tools. Every sentence is necessary and efficient.

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

Completeness3/5

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

Given the tool's complexity (5 parameters, external API calls, output schema), the description is somewhat sparse. It mentions the output type but does not elaborate on edge cases or caching. The output schema likely fills some gaps, but the description could be more complete.

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 input schema already documents each parameter. The description adds no additional meaning beyond what is in the schema, meeting the baseline of 3.

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 finds NDC/NDLC classification codes from subject terms using Web NDL Authorities and returns a suggested parameter and search call example. It explicitly distinguishes from sibling tools for reverse lookup and actual 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 provides explicit guidance on when to use this tool (searching classification codes from terms) and directs users to alternative tools for reverse lookup (jp_lit_find_authority_terms_by_classification) and actual literature search (jp_lit_search).

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