Skip to main content
Glama

Aviation & Space Weather Data (Tanod)

get_satellite_image

Read-onlyIdempotent

skypeek: Get a recent satellite image of a place or coordinates. For the forecast use get_weather. Returns a recent satellite picture of a place as a base64 PNG, with the capture date, cloud cover, source and attribution: the least cloudy recent Sentinel-2 L2A scene at 10 m per pixel as true colour, NDVI (vegetation) or NDWI (water), clouds painted grey in the index views; NASA GIBS true colour (about 250 m) for areas wider than 10 km or when Sentinel-2 has no scene. Not real time (date is the scene day); clouds can hide the ground (404 too_cloudy, no_scene, no_imagery: not charged). Sentinel-2 data is free to use with credit; NASA GIBS has no restrictions. Not for navigation or safety. Typically 5 to 25 s (a few Sentinel-2 tiles are read and rendered). Price: USD 0.01. Free: 5 skypeek calls per IP per UTC day. Docs: https://tanod.dev/learn/satellite-image-api.html

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_satellite_image"
  }
}

Input Schema

NameRequiredDescriptionDefault
latNoLatitude in degrees (-90 to 90). Send lat and lon, or place.
lonNoLongitude in degrees (-180 to 180). Send lat and lon, or place.
dateNoTarget day YYYY-MM-DD (2015-07 onward, not in the future): the nearest scene within 15 days that is clear enough. Default: the newest clear scene of the last 60 days.
sizeNoWidth and height of the PNG in pixels.
viewNotrue_color (a natural-colour picture), ndvi (vegetation) or ndwi (open water), both computed from the same Sentinel-2 scene with clouds painted grey.true_color
placeNoCity name, optionally with a country code (such as Manila, PH); cities of 15,000+ people. Send place, or lat and lon.
radius_mNoHalf the side of the pictured square, in metres (250-100000, default 2560: about 10 m per pixel at 512 px). Over 10000 is NASA 250 m true colour only.
max_cloudNoMost cloud accepted, as a percent of the pictured area. No scene that clear is a 404 too_cloudy (not charged).

Output Schema

NameRequiredDescriptionDefault
latNo
lonNo
bboxNo
dateNo
noteNo
viewNo
errorNoOnly on an error result: an object {code, message}, or the reason string of an x402 PaymentRequired object.
imageNo
placeNo
sceneNo
legendNo
sourceNo
fallbackNo
radius_mNo
upstreamNo
attributionNo
captured_atNo
resolution_mNo
cloud_cover_scene_pctNo
cloud_cover_window_pctNo
cloud_shadow_window_pctNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed18 schema fields changed
    • removedInput schema / properties / date / default
      Removed value: -null
    • removedInput schema / properties / date / title
      Removed value: -"Date"
    • removedInput schema / properties / lat / default
      Removed value: -null
    • removedInput schema / properties / lat / title
      Removed value: -"Lat"
    • removedInput schema / properties / lon / default
      Removed value: -null
    • removedInput schema / properties / lon / title
      Removed value: -"Lon"
    • changedInput schema / properties / max_cloud / description
      Previous value: -"Most cloud accepted, as a percent of the pictured area (0-100, default 30). No scene that clear is a 404 too_cloudy (not charged)."New value: +"Most cloud accepted, as a percent of the pictured area. No scene that clear is a 404 too_cloudy (not charged)."
    • removedInput schema / properties / max_cloud / title
      Removed value: -"Max Cloud"
    • removedInput schema / properties / place / default
      Removed value: -null
    • removedInput schema / properties / place / title
      Removed value: -"Place"
    • removedInput schema / properties / radius_m / title
      Removed value: -"Radius M"
    • changedInput schema / properties / size / description
      Previous value: -"Width and height of the PNG in pixels (128-1024, default 512)."New value: +"Width and height of the PNG in pixels."
    • removedInput schema / properties / size / title
      Removed value: -"Size"
    • removedInput schema / properties / view / title
      Removed value: -"View"
    • removedInput schema / title
      Removed value: -"get_satellite_imageArguments"
    • removedOutput schema / properties / bbox / items
      Removed value: -{
      -  "type": [
      -    "number",
      -    "null"
      -  ]
      -}
    • removedOutput schema / properties / image / properties
      Removed value: -{
      -  "bytes": {
      -    "type": [
      -      "integer",
      -      "null"
      -    ]
      -  },
      -  "content_type": {
      -    "type": [
      -      "string",
      -      "null"
      -    ]
      -  },
      -  "data_base64": {
      -    "type": [
      -      "string",
      -      "null"
      -    ]
      -  },
      -  "format": {
      -    "type": [
      -      "string",
      -      "null"
      -    ]
      -  },
      -  "height_px": {
      -    "type": [
      -      "integer",
      -      "null"
      -    ]
      -  },
      -  "width_px": {
      -    "type": [
      -      "integer",
      -      "null"
      -    ]
      -  }
      -}
    • removedOutput schema / properties / source / properties
      Removed value: -{
      -  "license": {
      -    "type": [
      -      "string",
      -      "null"
      -    ]
      -  },
      -  "name": {
      -    "type": [
      -      "string",
      -      "null"
      -    ]
      -  },
      -  "notice": {
      -    "type": [
      -      "string",
      -      "null"
      -    ]
      -  },
      -  "terms": {
      -    "type": [
      -      "string",
      -      "null"
      -    ]
      -  },
      -  "url": {
      -    "type": [
      -      "string",
      -      "null"
      -    ]
      -  }
      -}
  2. Added

TDQS

A4.6/5.0
Behavior5/5

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

Goes well past the read-only/idempotent annotations by disclosing latency (5-25 s), pricing (USD 0.01 per call), the free tier (5 calls per IP per UTC day), failure modes (404 too_cloudy, no_scene, no_imagery) and that failures are not charged, plus the licensing/attribution obligations for each source. It even explains how clouds are rendered grey in index views, which affects interpretation of the returned image.

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 and the sibling routing, and every clause carries usable information (source, resolution, fallback, errors, price, rate limit, licensing). The single dense paragraph is cramped and mixes operational, legal and quality-of-result details, which slightly hurts scannability.

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?

For an open-world, image-returning tool with an output schema already present, the description covers everything an agent needs to decide and call safely: source selection behavior, cloud rejection semantics, latency, cost, quota and licensing. Return-value structure is rightly left to the output schema rather than duplicated.

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 every parameter is already well documented, including the lat/lon vs place alternative, view enum, radius_m limits and the NASA fallback threshold. The description restates view modes and cloud painting but adds little syntax or format detail beyond the schema, so the baseline of 3 applies.

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?

States a specific verb and resource ("Get a recent satellite image of a place or coordinates") and immediately differentiates from the sibling: "For the forecast use get_weather." It also names the concrete output form (base64 PNG) and the underlying sources, so the agent knows exactly what it is calling.

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?

Explicit routing to get_weather for forecasts, an explicit exclusion ("Not for navigation or safety"), and a clear explanation of when the NASA GIBS fallback applies (areas wider than 10 km, or no Sentinel-2 scene). It also warns that the result is not real time because `date` is the scene day.

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.