Skip to main content
Glama

change_composite

Read-only

Composite 2-3 passes of one site into a change image.

Pass the STAC URLs of two or three acquisitions of the *same* site in time
order. Colors encode change: bright green = signal appeared after the first
date, magenta = signal vanished, grey = unchanged. Refuses to mix
polarizations (HH vs VV are not comparable). Returns the image block plus a
caption naming the color semantics and attribution -- and, when a pass carries
no polarization metadata so same-polarization could not be *verified*, a
structured caution text block naming that gap.

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

Input Schema

NameRequiredDescriptionDefault
dbNoDecibel stretch instead of a linear percentile stretch. Default false.
urlsYesSTAC JSON URLs or item ids of 2 or 3 passes, in time order. Mixed polarizations are refused.
assetNoProduct to composite. 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 composite. 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 2 or 3 passes, in time order. Mixed polarizations are refused."
  2. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations only declare readOnlyHint, so most of the behavioral load falls on the description, and it delivers: color encoding for appeared/vanished/unchanged signal, a hard refusal on mixed polarizations, and the exact return contents including the caption and the conditional structured caution block when polarization cannot be verified. This is disclosure of failure modes and output shape well beyond the annotation.

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?

Front-loaded with the purpose, then constraints, then return shape, with no filler sentences. The final sentence about the caution block is dense but it is carrying real behavioral information rather than restating the schema.

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?

There is no output schema, and the description compensates by describing the returned image block, caption content, and conditional caution block. Combined with the polarization refusal and ordering requirements, an agent has everything needed to call it correctly and interpret the result.

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 the baseline is 3. The description reinforces the 'same site' and time-order constraints on urls but does not explain the db, asset, or max_size parameters, so it adds only marginal meaning beyond the schema.

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 opening line gives a specific verb (composite) and a specific resource (a change image from 2-3 passes of one site). It is clearly distinguishable from narration-oriented siblings like narrate_change because it states the output is an image, and from single-pass tools like quicklook because it names the multi-pass composition.

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

Usage Guidelines4/5

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

It specifies the operational preconditions well: two or three acquisitions, the *same* site, supplied in time order, and same polarization. It does not explicitly name an alternative tool or state when a caller should prefer narration or a timescan over compositing, so routing guidance is inferable rather than stated.

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.