SkyFi MCP Server

get_bounding_box

Convert a named place into a GeoJSON bounding box polygon for use as an area of interest in satellite imagery search and order tools.

Instructions

Returns a bounding box polygon for a named place, directly usable as an AOI in search and order tools. Use this to convert a place name into a GeoJSON polygon for subsequent tool calls.

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": {
      "query": "<query>"
    },
    "name": "get_bounding_box"
  }
}

Input Schema

Name	Required	Description	Default
`query`	Yes	A named place to look up a bounding box for

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 10, 2026

TDQS

A3.8/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden. It discloses only the basic return type ('GeoJSON polygon') and the intended downstream use, but does not mention error behavior, side effects, authentication, or limitations. This is minimal behavioral disclosure.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with the primary action, and no filler. Every word contributes to understanding the tool's purpose and usage.

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?

For a simple single-parameter tool, the description is almost complete: it states the return type (GeoJSON polygon) and the use case (AOI for search/order). It lacks details like error handling or coordinate reference system, but these are not critical for an AI agent to invoke the tool 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?

The input schema already fully documents the single 'query' parameter with a clear description ('A named place to look up a bounding box for'). The tool description adds no new parameter-specific meaning, 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?

The description clearly states the tool 'Returns a bounding box polygon for a named place' with a specific verb and resource. The phrase 'directly usable as an AOI in search and order tools' adds a distinguishing use-case, differentiating it from siblings like geocode that return coordinates rather than polygons.

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?

Explicitly instructs 'Use this to convert a place name into a GeoJSON polygon for subsequent tool calls,' providing clear context for when to invoke it. It does not list explicit exclusions or alternatives, but the usage intent is unmistakable.

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