Skip to main content
Glama

Get a preview

get_preview
Read-onlyIdempotent

Status of a preview and, when ready, the directions with their QA. Free.

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": {
      "preview_id": "<preview_id>"
    },
    "name": "get_preview"
  }
}

Input Schema

NameRequiredDescriptionDefault
preview_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.8/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent and non-destructive, so safety is covered. The description adds useful behavior beyond them: the response depends on state (status, and only when ready the directions with QA) and that the call is free of cost. It does not say what happens when the preview is not ready or whether polling is expected.

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?

Two short fragments with no filler, and the core payload (status, then directions with QA) is front-loaded. The telegraphic style and the dangling 'Free' slightly hurt readability, but nothing is wasted.

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?

For a simple one-parameter read tool with no output schema, the description does outline the return contents and a state-dependent branch. It is still thin on the not-ready case, error behavior, and where preview_id comes from, which matters given no output schema to fall back on.

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 description coverage is 0% and the single parameter preview_id is never mentioned in the description, so no meaning is added beyond the schema. The parameter is largely self-explanatory by name, but the description does not state accepted format, source of the id, or behavior for unknown ids.

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

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the resource (a preview) and says it returns status, plus directions with QA when ready, which is more than a restatement of the name. However, the phrasing is fragmentary ('Status of a preview and...') with no explicit verb, and the trailing 'Free' is ambiguous as to purpose. An agent can guess it is a read of preview state but not precisely what it returns.

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 guidance and no mention of alternatives such as create_preview, even though the sibling list shows a create/preview pair. The only implied guidance is that this is the retrieval counterpart to creation, which the agent must infer.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources