Skip to main content
Glama

jp_lit_search_kaken_projects

Search KAKEN for research projects by theme, keyword, or researcher. Retrieve project details including report PDFs and output previews for verification in other databases.

Instructions

KAKEN から研究課題を検索し、研究テーマ・キーワード・報告書 PDF・成果リストの手がかりを返す補助 tool。論文・図書の文献確定は CiNii / J-STAGE / IRDB / NDL で再確認する

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesKAKEN から探す研究課題名・キーワード・研究テーマ。
limitNo返す研究課題候補の最大件数。最大 20。
pageNo検索結果ページ番号。1 始まり。
detail_limitNo詳細ページを追加取得する候補数。0 なら詳細取得しない。最大 10。
researcher_nameNo研究代表者・研究分担者名で絞る場合に指定する。
from_fiscal_yearNo研究期間の開始年度下限。
to_fiscal_yearNo研究期間の終了年度上限。
include_outputsNotrue の場合は成果リスト preview も取得する。文献確定は CiNii / J-STAGE / IRDB / NDL で再確認する。
force_refreshNotrue の場合はローカル cache を使わず upstream API から再取得する。false の場合は保存済み cache を優先する。

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYes
pageYes
limitYes
totalYes
itemsYes
cacheNo
Behavior2/5

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

With no annotations, the description must fully disclose behavior. It mentions results are 'clues' and recommends rechecking elsewhere, but lacks details on limitations, data freshness, authentication needs, or caching behavior (only implied by a parameter). Insufficient for a 9-parameter tool.

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?

Two sentences, front-loaded with core purpose, no wasted words. Highly 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 complexity (9 params, no annotations) and existence of an output schema (which likely covers return values), the description is adequate but lacks usage hints, preconditions, or edge-case handling. Less complete than ideal.

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 is 3. The description does not add meaning beyond the schema's own parameter descriptions. No parameter-specific guidance or examples 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?

Description clearly identifies the tool as searching KAKEN for research projects and returning themes, keywords, report PDFs, and output clues. It distinguishes from siblings by noting it is an auxiliary tool for preliminary search, while final confirmation should use other databases.

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?

Usage is implied as a preliminary search tool for KAKEN projects, but no explicit when-to-use or when-not-to-use guidance is provided. No alternatives or exclusions are mentioned, leaving the agent to infer context.

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