Skip to main content
Glama

moonlight_prepare_question

Prepares a question for a specified Moonlight tab without sending it, returning a requestId that requires popup confirmation before submission.

Instructions

准备一条给 Moonlight 的问题,不填入也不发送。返回 requestId,用户需在扩展弹窗逐次确认;确认后才可 submit。

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>",
      "question": "<question>"
    },
    "name": "moonlight_prepare_question"
  }
}

Input Schema

NameRequiredDescriptionDefault
tabIdYesmoonlight_tabs 返回的 tabId
questionYes

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?

Annotations already declare readOnlyHint=false, idempotentHint=false and openWorldHint=true; the description goes beyond them by disclosing the human-in-the-loop gate (per-request confirmation in the extension popup) and that the call returns a requestId rather than acting. It does not say whether repeated calls create duplicate pending requests, whether the requestId expires, or what happens if the user declines.

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 sentences, front-loaded with what the tool does and does not do before the workflow constraint. Every clause carries information; there is no filler.

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 staged-write gate with no output schema, the description supplies the critical missing pieces: the requestId return value and the confirmation prerequisite before submit. Remaining gaps are requestId lifetime and behavior on user cancellation, which are secondary but would matter for retry logic.

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

Parameters2/5

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

Schema coverage is only 50%: tabId is documented in the schema as coming from moonlight_tabs, but question has no schema description at all. The description adds nothing about the question field (content expectations, the 12000-character cap, whether it is plain text), so it fails to compensate for the documented gap and merely restates the tool's own purpose.

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

Purpose5/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 (prepare a question for Moonlight) and immediately negates two adjacent behaviors (不填入也不发送), which cleanly separates it from moonlight_submit_question. An agent can tell what this does and what it deliberately does not do without opening the schema.

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 states the workflow position: prepare here, then the user confirms in the extension popup, and only then may submit be called. That effectively routes the agent to moonlight_submit_question as the follow-up step. It does not state conditions under which this tool should be skipped (e.g., an already-pending request), so it falls short of full when/when-not guidance.

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