Skip to main content
Glama
Eclipse-Cj

Paper Distill MCP Server

by Eclipse-Cj
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

init_session

Initialize a research session by setting up push channels and loading previous context. Detects configured platforms and manages channels for streamlined research.

Instructions

Initialize a research session. Call this first to set up push channels and load context.

Detects configured platforms, manages channels, and optionally loads previous research context. Returns session info for the AI client to present to the user.

IMPORTANT for AI clients:

  • NEVER call external APIs (Zotero, webhooks, etc.) directly or generate scripts (PowerShell, curl, Python) to do so. Always use the built-in tools (collect, collect_to_zotero, send_push, etc.). Direct API calls will result in incomplete data and encoding issues.

  • If multiple platforms are detected and no platform is specified, the response will include ask_platform — you MUST ask the user which platform to use, then call init_session again with platform=<user_choice>.

  • If only one platform is configured, it is auto-selected.

  • The send_push tool also accepts a platform parameter, so the user can override per-push even after init.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
platformNoPreferred push platform ("telegram", "discord", "feishu", "wecom"). If None, auto-detects from configured env vars.
session_idNoSession identifier (auto-generated if not provided). Use different IDs to isolate research vs daily topics.
load_contextNo"yes" = auto-load previous research context, "no" = start fresh, "ask" = return context summary for user to decide.ask
channel_actionNo"new" = create dedicated channel, "existing" = use configured channel, "auto" = use existing if available.auto

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Tool Definition Quality

A4.7/5.0
Behavior4/5

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

No annotations provided, but description discloses platform detection, channel management, optional context loading, and warnings against direct API calls. Could mention potential side effects like channel creation more explicitly.

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?

Well-structured with summary and bullet points; every sentence is valuable. Slightly long but justified by complexity. Clear callouts for AI clients.

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?

Covers initialization, platform handling, user interaction, and behavior of all 4 parameters. Mentions output (session info). Minor omission of idempotency but not critical.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Adds significant meaning beyond schema: explains auto-detection for platform, isolation for session_id, three options for load_context and channel_action. Schema coverage is 100% but description still adds value.

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 initializes a research session as a first step, with specific verbs (initialize, set up, load) and distinguishes it from siblings like load_session_context.

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?

Explicit guidance on when to call this tool first, never using external APIs, how to handle multiple platforms (must ask user), auto-selection for single platform, and interaction with send_push tool.

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/Eclipse-Cj/paper-distill-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server