Skip to main content
Glama
Sign In
velocity

velocity

by AndrewCTF
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

sar_scenes

Retrieve recent keyless Sentinel-1 SAR scenes for a bounding box and optionally detect radar ship contacts, including dark vessels where AIS coverage is absent.

Instructions

Recent keyless Sentinel-1 SAR scenes over a box, for water AIS does not reach. bbox = lon0,lat0,lon1,lat1. By default a SCENE INVENTORY (id, time, footprint, public download URL). detect=True also returns LOCATED radar contacts for a box up to one degree a side, each classified against AIS: 'dark' only where enough nearby AIS makes absence meaningful, otherwise 'unknown'. Read note: it says when detection did not run and why.

Input Schema

NameRequiredDescriptionDefault
bboxYes
daysNo
limitNo
detailNoshort
detectNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

A4.1/5.0
Behavior4/5

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

Since no annotations are provided, the description must do the heavy lifting. It successfully describes the output structure (Scene Inventory fields, 'dark' vs 'unknown' classifications) and includes a critical behavioral warning about checking a 'note' for detection failures.

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 description is dense but well-structured, front-loading the main purpose (SAR scenes over a box). It avoids unnecessary fluff and uses parentheses to convey technical details about the bbox format.

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 description is exceptionally complete given the lack of structured metadata. It covers the input format, the dual nature of the output, and a crucial fallback/failure condition regarding the detection process.

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?

Because schema coverage is 0%, the description must explain all 5 parameters. It only provides semantic details for 'bbox' (format) and 'detect' (behavioral outcome), leaving the function of 'days', 'limit', and 'detail' entirely undocumented in the text.

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 purpose is crystal clear: providing recent Sentinel-1 SAR scenes over a specified area. It explicitly mentions two distinct behaviors (scene inventory vs. radar contact detection), making it highly specific to its function.

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 defines a key use case: when 'water AIS does not reach.' It also differentiates usage based on setting the 'detect' parameter, guiding the agent on when to expect simple scene metadata versus complex radar classification.

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

Deploy Server

Other Tools