Skip to main content
Glama

quicklook

Read-only

Return a scene's quicklook PNG as an image block.

Prefers a baked catalog preview (``preview="auto"``, the default) so a
public host can show the radar scene without proxying Umbra COGs.
**A baked preview is typically 512 px** (the published weekly sidecar).
``max_size`` applies only to a fresh ``preview="render"`` stream; when a
cached thumbnail is smaller than requested, the caption says
``max_size`` was ignored *and* includes a JSON
``{"image": {source, width, height, requested_max_size, substituted}}``
sidecar. For a higher-resolution picture (typically 1024 px), run a
local ``uvx --from 'umbra-py[mcp]' umbra-mcp`` server, or download the
GEC href from ``get_item``. ``preview="baked"`` refuses rather than
stream; ``preview="render"`` always streams (needs ``[viz]``, refused
on ``umbra serve --public``).

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": {
      "url": "<url>"
    },
    "name": "quicklook"
  }
}

Input Schema

NameRequiredDescriptionDefault
dbNoDecibel stretch for a fresh render. Default false. A baked preview is always decibel.
urlYesSTAC JSON URL or index item id. The public host also accepts a product filename or acquisition stem that is in the index.
assetNoProduct to show. Default GEC. A baked preview is used only when its recorded product matches, or when it recorded none and this is GEC.GEC
previewNoauto (default) uses a baked preview when present, else renders. baked refuses if none. render always streams a COG and is refused on the public host.auto
max_sizeNoLongest side in pixels for a fresh render. Default 1024. Ignored when a smaller baked preview is returned.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedInput schema / properties / asset / description
      Added value: +"Product to show. Default GEC. A baked preview is used only when its recorded product matches, or when it recorded none and this is GEC."
    • addedInput schema / properties / db / description
      Added value: +"Decibel stretch for a fresh render. Default false. A baked preview is always decibel."
    • addedInput schema / properties / max_size / description
      Added value: +"Longest side in pixels for a fresh render. Default 1024. Ignored when a smaller baked preview is returned."
    • addedInput schema / properties / preview / description
      Added value: +"auto (default) uses a baked preview when present, else renders. baked refuses if none. render always streams a COG and is refused on the public host."
    • addedInput schema / properties / url / description
      Added value: +"STAC JSON URL or index item id. The public host also accepts a product filename or acquisition stem that is in the index."
  2. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations only declare readOnlyHint, so the description carries useful extra weight: it discloses refusal semantics for preview="baked", the public-host restriction for render, the fact that max_size may be silently ignored with a caption note, and the JSON sidecar fields. It adds real behavioral context beyond what annotations provide.

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?

The key action is front-loaded in the first sentence and the mode/size caveats follow logically. It is dense with inline code and a literal JSON blob, which is informative but adds visual clutter and length; a slightly tighter phrasing would earn a 5.

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?

With no output schema, the description does the necessary work of explaining what comes back (an image block plus a caption and, when substitution occurs, an image sidecar) and what typical resolutions to expect. Minor gaps remain, such as the image block's shape/metadata, but nothing essential to correct invocation is missing.

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 coverage is already 100%, so the baseline is 3, but the description adds cross-parameter meaning the schema does not: max_size applies only to a fresh render and is ignored for a smaller baked preview, and the baked/render distinction constrains how preview interacts with asset matching. It stops short of clarifying db behavior beyond what the schema says.

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 first sentence states a concrete verb and resource ('Return a scene's quicklook PNG as an image block') and the rest of the description makes clear how it differs from fetching raw data via get_item. An agent can distinguish this image-returning tool from catalog/download tools 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 Guidelines5/5

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

Explicitly states the default path (preview="auto"), what baked vs render do, that render is refused on the public host, and routes to alternatives by name for higher resolution (local umbra-mcp server, or the GEC href from get_item). This is when-to-use and when-not-to-use guidance with named alternatives.

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.