Skip to main content
Glama

timescan

Read-only

Summarize a whole time series into one activity image.

Pass the STAC URLs of a site's passes; the timescan encodes per-pixel
temporal statistics so bright/colored areas are *where activity happened*
over the series. Returns the image block plus attribution.

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": {
      "urls": "<urls>"
    },
    "name": "timescan"
  }
}

Input Schema

NameRequiredDescriptionDefault
dbNoDecibel stretch instead of a linear percentile stretch. Default false.
urlsYesSTAC JSON URLs or item ids of at least two passes of one site.
assetNoProduct to scan. Default GEC.GEC
max_sizeNoOverview size cap in pixels for each pass. Default 1024.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / asset / description
      Added value: +"Product to scan. Default GEC."
    • addedInput schema / properties / db / description
      Added value: +"Decibel stretch instead of a linear percentile stretch. Default false."
    • addedInput schema / properties / max_size / description
      Added value: +"Overview size cap in pixels for each pass. Default 1024."
    • addedInput schema / properties / urls / description
      Added value: +"STAC JSON URLs or item ids of at least two passes of one site."
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=true, so the description carries most of the burden and does add value: it discloses the return content ('image block plus attribution') and explains how to read the output (bright/colored areas mark where activity happened). It does not mention rate limits, cost, or behavior when passes are misaligned, which keeps it short of a 5.

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 tight sentences with the core action front-loaded and the output interpretation second. The markdown emphasis is slightly decorative but not wasteful; nothing is redundant.

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 compensates by naming the return payload (image block plus attribution) and explaining how to interpret the rendering. For a four-parameter read-only image tool, that covers what an agent needs to call and use it correctly.

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

Parameters3/5

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

Schema description coverage is 100%, so url, db, asset, and max_size are already documented in the schema. The description restates that urls are STAC references to a site's passes and adds the 'at least two' constraint, but contributes no new meaning about db, asset, or max_size.

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 specific verb and resource ('Summarize a whole time series into one activity image') and explains what the resulting image represents. It does not explicitly differentiate itself from near-neighbors such as change_composite or quicklook, so an agent must infer which composite-style tool to pick.

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?

'Pass the STAC URLs of a site's passes' gives an implicit precondition (multiple passes from a single site), and the schema reinforces 'at least two.' There is no explicit when-to-use versus alternatives, nor any exclusions for cases where a quicklook or change composite would be better.

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.