Skip to main content
Glama

moonlight_status

Read-onlyIdempotent

Check local connection and Chrome extension status before reading papers; call this first to confirm Moonlight Reader is ready and avoid setup errors.

Instructions

检查本地连接和 Chrome 扩展状态。首次使用先调用此工具。

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "moonlight_status"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A4.1/5.0
Behavior4/5

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

The annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds the workflow constraint that this acts as a prerequisite gate on first use, which is real context beyond the annotations. It doesn't elaborate on the openWorld dependency on a local Chrome extension, which is the riskiest part of the behavior.

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 functional purpose first and the usage directive second, and nothing redundant. Every sentence adds information the agent needs.

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 simple, zero-parameter diagnostic, the description is close to adequate. The remaining gap is that with no output schema, the description doesn't indicate the shape of the returned statuses, or how a failure surfaces, which an agent would want to know in order to decide whether to proceed.

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

Parameters4/5

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

The tool takes zero parameters, so there is nothing this dimension needs to explain beyond that fact. The baseline treatment for a zero-parameter tool applies.

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 two concrete resources: it checks both the local connection and the Chrome extension status. This immediately separates it from every sibling (annotations, library, tabs, paper operations), although it doesn't explicitly name a distinguishing alternative.

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 an explicit triggering condition, requiring the agent to call it before first use, which is exactly the kind of guidance an agent needs. It stops short of describing what to do when the check fails, or whether a re-check is ever warranted mid-session.

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