Skip to main content
Glama

moonlight_library

Idempotent

Reads papers already shown in the Moonlight library tab and filters them by title, returning the search scope and hasMore so partial results aren’t mistaken for the full collection.

Instructions

读取论文库中已呈现的论文并按标题筛选。需使用 /library 标签页。返回检索范围与 hasMore;不要把部分列表当成全部文献。

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_library"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNo
tabIdYesmoonlight_tabs 返回的 tabId
maxPagesNo

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, it discloses return values (search scope and hasMore) and an important caveat about partial results, which directly supports the maxPages pagination model. It does not address the tension with readOnlyHint=false (why does reading alter state?) or the browser/tab side effects implied by openWorldHint=true.

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?

Three short sentences, with the action stated first, then the tab prerequisite, then the return and pagination caveat. There is no filler, though the tab requirement could be merged more tightly with the filtering statement.

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

Completeness3/5

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

There is no output schema, so the description responsibly names the key return fields (scope and hasMore). However, for an open-world browser-backed tool, it omits tab-state effects and the meaning and cost of maxPages, leaving an agent to infer pagination behavior.

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?

With only 33% schema coverage, the description must compensate, and it partly does: it clarifies that query means title filtering and that tabId must correspond to the /library tab, which moonlight_tabs returns. The maxPages parameter is only indirectly implied by the partial-list warning and is never explained.

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 action and resource: it reads papers already rendered in the paper library and filters them by title ("读取论文库中已呈现的论文并按标题筛选"). This distinguishes it from siblings like moonlight_paper or moonlight_open_paper, which likely fetch or open individual papers, but it does not name those siblings explicitly.

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?

It gives a clear precondition: the /library tab must be in use ("需使用 /library 标签页"). It also warns not to treat a partial list as the complete literature. However, it names no alternative tool and gives no explicit when-not guidance.

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