Skip to main content
Glama

moonlight_open_paper

Idempotent

Opens a paper by Moonlight paperId, reusing an existing page or creating a background tab, and returns a tabId for reading metadata after the page loads.

Instructions

按 Moonlight paperId 打开论文。复用已打开页面,否则新建后台标签页;返回 tabId,页面加载后可读取元数据。

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "paperId": "<paperId>"
    },
    "name": "moonlight_open_paper"
  }
}

Input Schema

NameRequiredDescriptionDefault
paperIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A3.8/5.0
Behavior4/5

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

Beyond the annotations (readOnlyHint=false, idempotentHint=true, openWorldHint=true), the description discloses that a background tab is created rather than a focused one, that existing pages are reused, and that the call returns a tabId. Those are real behavioral facts an agent needs. It does not cover permission or authentication needs, or what happens if the paperId is unknown.

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 short sentences, front-loaded with the action and then the tab-reuse/return-value detail. Nothing is redundant and nothing could be cut without losing information.

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?

For a single-parameter tool with no output schema, the description covers the action, the side effect (background tab), the return value (tabId), and the follow-up (read metadata after load). Annotations supply the safety profile. Only a fallback or permissions detail is missing.

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 schema has 0% description coverage, but the description compensates by naming the parameter as a Moonlight paperId, which implies that callers should pass a Moonlight-native identifier rather than, say, a DOI or a URL. The schema already supplies the UUID format and pattern, so the description adds only this piece of meaning.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource ('open a paper by Moonlight paperId'), so an agent immediately knows the action and the identifier space. It does not distinguish itself from siblings such as moonlight_tabs or moonlight_paper, which keeps it short of a 5.

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 rather than stated: it tells the agent that an existing page is reused and that metadata can be read once the page has loaded, which hints at the open-then-read workflow. It never says when to prefer this over a sibling such as moonlight_tabs, and it states no exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.