Skip to main content
Glama

list_previews

Read-onlyIdempotent

Retrieves running dev-server previews, including ID, URL, displayed content, and page-check status.

Instructions

The running dev-server previews: id, url, what they show and the page check.

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": "list_previews"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.0.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety and repeatability profile is fully covered. The description adds that these are *running* previews and reveals the return fields (id, url, content description, page check), which is genuine added context. It stops short of saying what happens when no dev server is running or how the 'page check' should be interpreted.

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?

A single compact line with no wasted words, and the resource ('running dev-server previews') is front-loaded before the field list. The telegraphic fragment style is efficient but slightly less scannable than a complete sentence would be.

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?

With no output schema, listing the returned fields is the right move, but 'what they show and the page check' is vague — an agent cannot tell whether 'page check' is a status, a boolean, or an error report. For a trivial zero-argument read tool this is close to sufficient, yet the undefined return field leaves a real gap.

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 for the description to disambiguate and the baseline of 4 applies. The input schema is an empty, closed object, consistent with the description implying no arguments.

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?

Names a specific resource — running dev-server previews — and implicitly the listing operation, so an agent can tell it apart from the meeting/collaboration list siblings by resource alone. The verb is elided (the description is a noun phrase), which keeps it just short of a fully explicit 'list X' statement.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use, when-not-to-use, or alternative routing guidance; the description only says what the data is. An agent must infer that this is the discovery call for previews before acting on them.

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