Skip to main content
Glama

moonlight_submit_question

Idempotent

Submits an approved AI question to a Moonlight Reader tab after popup confirmation; retrieve the answer with read_ai. Sends each requestId once and does not auto-retry.

Instructions

发送扩展弹窗已经确认的准确问题。可能消耗 Moonlight 额度。每个 requestId 只尝试发送一次,超时或连接中断都不自动重发。发送后用 read_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>",
      "requestId": "<requestId>"
    },
    "name": "moonlight_submit_question"
  }
}

Input Schema

NameRequiredDescriptionDefault
tabIdYesmoonlight_tabs 返回的 tabId
requestIdYes

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?

Beyond the annotations (write, open-world, idempotent, non-destructive), it discloses the Moonlight quota cost and the no-auto-resend policy on timeout or connection loss, which is critical operational context. It doesn't say what happens to a partially sent request or whether quota is consumed on failure, so it stops short of full disclosure.

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?

Three short sentences with no wasted wording: action first, then cost warning, then retry semantics, then the required follow-up. Every sentence carries information an agent needs before invoking.

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 2-parameter tool with no output schema, the description covers the precondition, the cost, the retry policy, and where to get results (read_ai). Error response shape is not described, but that is a minor gap given results are explicitly deferred to a sibling tool.

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?

Schema description coverage is 50%: tabId is documented in the schema, but requestId has only a regex pattern. The description compensates by explaining requestId's role as a one-attempt idempotency key ('每个 requestId 只尝试发送一次'), which is meaning the schema does not convey.

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 definition states a specific verb+resource: send the exact question already confirmed in the extension popup. 'Since it has already been confirmed' implicitly separates it from moonlight_prepare_question, and it names moonlight_read_ai as the follow-up. It doesn't explicitly name the sibling it replaces, so it falls just short of full sibling differentiation.

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?

The description places the tool in a clear flow: the question has already been confirmed in the popup, then submit, then call read_ai to retrieve results. It gives no explicit 'do not use this when…' exclusions, but the precondition (already confirmed) is a usable selection cue.

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