Skip to main content
Glama

moonlight_read_ai

Idempotent

Reads existing Moonlight summaries, explanations, and current discussions for a specified tab, clearly marking Moonlight-generated content without generating or sending anything.

Instructions

读取 Moonlight 已有摘要、解释和当前讨论。返回内容明确标注 Moonlight 生成。不会点击生成或发送。

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

Input Schema

NameRequiredDescriptionDefault
tabIdYesmoonlight_tabs 返回的 tabId

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

B3.4/5.0
Behavior3/5

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

The annotations already declare destructive=false, idempotent=true and openWorld=true; the description adds useful context by stating content is explicitly labeled as Moonlight-generated (provenance) and that no generate/send action is triggered. However, it does not explain what happens when no summary exists, whether a tab must first be opened, or why readOnlyHint is false despite the read framing.

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, front-loaded with what is read, followed by provenance and the negative action constraint. No filler, though the sentences are terse enough that some behavioral context was dropped rather than compressed.

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?

For a one-parameter read tool with no output schema and full schema coverage, the essentials are present, but edge cases (no existing summary, prerequisite tab state) and the readOnlyHint=false annotation are left unexplained.

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 coverage is 100% and the single tabId parameter is documented as coming from moonlight_tabs, so the schema already carries the meaning. The description adds nothing about the parameter, which is acceptable at full coverage but leaves no extra value.

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 a specific verb and resource: reading Moonlight's existing summaries, explanations and current discussion. That distinguishes it from generating siblings, though it does not name which sibling to use instead when the agent wants the paper itself or annotations.

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?

"Will not click generate or send" implies a clear when-not boundary (no triggering generation), but the when-to-use case is only implicit: read content that already exists. No alternative tool is named for fetching a paper or its annotations, so the agent must infer routing from sibling names.

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