Skip to main content
Glama

moonlight_paper

Read-onlyIdempotent

Retrieve paper metadata, page count, rendered page numbers, and original PDF links from a Moonlight tab to verify source content instead of treating AI summaries as original text.

Instructions

读取论文元信息、页数、已渲染页码和页面提供的原 PDF 链接。不会将 AI 摘要作为原文。

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": {
      "tabId": "<tabId>"
    },
    "name": "moonlight_paper"
  }
}

Input Schema

NameRequiredDescriptionDefault
tabIdYesmoonlight_tabs 返回的 tabId

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?

Annotations already declare readOnly, idempotent, non-destructive, and openWorld, so the safety profile is covered. The description adds genuinely new behavioral context: it enumerates what is returned and explicitly rules out substituting AI summaries for original text, which is a meaningful fidelity guarantee. It does not cover failure modes, such as an unrendered or invalid tabId.

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, with the returned fields front-loaded and the fidelity caveat second. Nothing is redundant, and no sentence 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?

With no output schema, the description still tells the agent what it gets back (metadata, page count, rendered pages, PDF link), which is the critical information. Minor gaps remain around the relationship to moonlight_pages and error behavior, but the definition is sufficient to call the tool correctly.

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%, and the single tabId parameter is documented in the schema as coming from moonlight_tabs. The description adds no further meaning about tabId, which is acceptable at full coverage but earns only the baseline.

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 names the specific resources returned: paper metadata, page count, rendered page numbers, and the original PDF link ("读取论文元信息、页数、已渲染页码和页面提供的原 PDF 链接"). It also implicitly distinguishes itself from AI-summary siblings by stating it will not pass AI summaries off as original text, though it does not name any sibling explicitly.

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?

The caveat "不会将 AI 摘要作为原文" implies this is the tool to use when authoritative source metadata and original-text pointers are needed rather than AI-generated summaries. However, it never explicitly says when to choose this over moonlight_open_paper or moonlight_pages, so the routing is left to inference.

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