Skip to main content
Glama

Umbra open SAR archive

by io.github.reesehammer
OverviewDiscussionsAdmin

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``).

Input Schema

NameRequiredDescriptionDefault
dbNo
urlYes
assetNoGEC
previewNoauto
max_sizeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Since annotations are minimal (`readOnlyHint: true`), the description bears the full burden and excels. It explains critical operational behaviors like caching (that `max_size` is ignored when a cached thumbnail is smaller) and the generation of JSON sidecars.

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?

While the description is lengthy, its complexity (caching, rendering modes, environment dependencies) necessitates the detail. The most critical information—the purpose and default behavior—is placed upfront.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The definition is highly complete. It outlines the return type, operational limits (refusal vs. streaming), resolution behavior, and external requirements for high resolution (e.g., local server/`get_item`), leaving no major functional gaps for the agent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage, the description provides vital semantic context for each parameter. It explains the functional meaning of `preview` (baked, render) and how `max_size` interacts with the caching mechanism, adding significant meaning beyond simple schema typing.

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 description clearly identifies the resource ('a scene's quicklook PNG') and the action ('Return'). It differentiates itself from general asset retrieval by specifying the format (PNG image block) and the underlying logic of the 'quicklook' function.

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?

It provides specific usage constraints, explaining that baked previews prefer `preview="auto"` and detail the conditional behaviors of `preview="baked"` (refuses) versus `preview="render"` (streams, requires [viz]). This tells the agent exactly when different modes are viable.

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

All Umbra open SAR archive toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources