Skip to main content
Glama

jp_lit_search_kaken_projects

Search KAKEN research projects by keyword, researcher name, or fiscal year. Retrieve project themes, keywords, PDF reports, and output lists for literature verification.

Instructions

external read / local bookkeeping write(非破壊)。KAKEN から研究課題を検索し、研究テーマ・キーワード・報告書 PDF・成果リストの手がかりを返す補助 tool。論文・図書の文献確定は CiNii / J-STAGE / IRDB / NDL で再確認する 外部sourceは変更しない。cache hitでもlocal session履歴を更新し、cache missまたはforce_refreshではlocal cacheを作成・置換する。

Input Schema

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

Output Schema

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

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

The description discloses local bookkeeping writes (cache and session history updates) without modifying external sources. It explains cache hit/miss behavior and force_refresh, which goes beyond the annotations (readOnlyHint=false, destructiveHint=false) to clarify the non-destructive nature.

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 concise but packs essential information: purpose, scope, caching, and limitations. The opening phrase 'external read / local bookkeeping write' effectively categorizes the tool. While clear, it could be structured into clearer sections for improved readability.

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 tool's complexity (9 parameters, caching, output schema), the description covers the overall workflow, non-destructive behavior, stateful caching, and instructions to use other databases for final verification. This provides sufficient context for correct use alongside the output schema.

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?

The input schema has 100% parameter description coverage, so the schema already explains each parameter. The description adds no parameter-specific details beyond the schema, meeting the baseline for high coverage. No further value is added for parameter understanding.

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 searches KAKEN for research projects, returning themes, keywords, report PDFs, and output clues. It distinguishes from siblings by specifying the KAKEN scope and is explicitly a supplementary tool for project discovery, not final literature verification.

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

Usage Guidelines4/5

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

The description advises re-confirming literature in CiNii/J-STAGE/IRDB/NDL, implying this tool is for initial project retrieval, not final records. It also notes external sources are unchanged. However, it does not explicitly compare with sibling tools like jp_lit_search or jp_lit_search_fulltext.

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