Skip to main content
Glama

moonlight_tabs

Read-onlyIdempotent

Lists reader tabs available in the current browser, excluding other websites, so clients can discover which Moonlight tabs they can work with.

Instructions

列出当前浏览器中可用的 Moonlight 标签页。不返回其他网站。

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds one useful behavioral fact beyond that — results are restricted to Moonlight tabs and exclude other sites — but says nothing about ordering, counts, or whether tab identifiers/URLs are returned. A 3 is appropriate given the annotation coverage.

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, the scope statement front-loaded immediately after the action. Every clause carries information; nothing is redundant or padded.

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 zero-parameter, read-only enumeration tool with complete annotations, the description covers what the tool returns and the key scoping constraint. The only gap is the shape of the returned tab entries (fields, ordering), which is modest since no output schema exists and the tool is otherwise trivially callable.

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 the empty schema is fully self-documenting and there is nothing for the description to disambiguate. Baseline of 4 applies since no compensating parameter explanation is needed.

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?

States a concrete verb ("列出"/list) and a specific resource ("Moonlight 标签页"/Moonlight tabs), plus a scope qualifier that excludes non-Moonlight sites. It is distinguishable from siblings like moonlight_pages or moonlight_library, though it does not explicitly name which sibling to use when the agent wants page content rather than a tab list.

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?

Usage is only implied: an agent can infer this is the discovery step before operating on a tab, but the description never states when to prefer it over moonlight_pages or moonlight_status, nor any preconditions. No explicit when-not guidance or named alternative is given.

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