Skip to main content
Glama

jp_lit_annotate_session

Annotate selected search results with labels and notes to indicate adoption, hold, or weak candidate status, without altering the original results.

Instructions

write: session。現在の調査セッション内で、既存の検索・書誌取得結果に候補ラベルと短いメモを保存する。未選別結果そのものや cache は変更せず、採否・保留・弱候補などの選別判断だけを追加する。調査全体の目的・未確認事項・次アクションは jp_lit_update_session_trace、単なる履歴検索には jp_lit_find_sessions / jp_lit_list_sessions を使う

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toolYes注釈対象の結果を生成した tool 名。通常は jp_lit_search または jp_lit_refine_results。
notesNoこの注釈 entry 全体に対する補足メモ。
traceNo検索意図、判断、根拠確認範囲などの調査経過。
cache_keyYes保存済み tool 実行結果を指す cache_key。jp_lit_search や cache 一覧 tool の戻り値から渡す。
selected_itemsYes現在の調査セッションに保存する選別済み候補。未選別の検索結果そのものは変更しない。

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
session_idYes
updated_atYes
annotated_countYes
Behavior5/5

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

Annotations indicate it is a write operation (readOnlyHint=false) and not destructive (destructiveHint=false). The description confirms it writes but does not modify raw results or cache, adding context about what is saved and what remains unchanged. No contradiction with annotations.

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 reasonably concise, front-loading the key action 'write: session' and then elaborating. However, it could be slightly more structured for readability.

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

Completeness4/5

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

Given the complexity with many parameters and nested objects, the description covers the core functionality well, distinguishing from siblings. It does not explain return values, but an output schema exists. Could mention the overall workflow more explicitly.

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 baseline is 3. The description adds high-level context for the main required parameters (tool, cache_key, selected_items) but does not provide significant additional meaning beyond the schema's descriptions. The nested objects are not explained in the tool description.

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 writes labels and notes to existing search/bibliographic results within the current session, without modifying raw results or cache. It distinguishes this tool from siblings like jp_lit_update_session_trace and jp_lit_find_sessions/list_sessions by purpose.

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?

Explicitly tells when to use this tool (annotating existing session results) and when to use alternatives: overall goals/trace via jp_lit_update_session_trace, history search via jp_lit_find_sessions/list_sessions. Also clarifies it does not modify raw results.

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