SkyFi MCP Server

quote_archive_order

Generate a binding quote for an archive order, providing the quote ID and purchase details for confirmation before executing the order.

Instructions

Generate a binding quote for an archive order. Returns a quote_id (valid 15 minutes) and a human-readable summary of what will be purchased and at what price. Present this to the user and wait for explicit confirmation before calling execute_archive_order.

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": {
      "archive_id": "<archive_id>",
      "aoi": "<aoi>",
      "price_per_sqkm_usd": "<price_per_sqkm_usd>",
      "price_full_scene_usd": "<price_full_scene_usd>",
      "overlap_sqkm": "<overlap_sqkm>"
    },
    "name": "quote_archive_order"
  }
}

Input Schema

Name	Required	Description
`aoi`	Yes	GeoJSON Polygon for the order area — must overlap the archive footprint
`archive_id`	Yes	Archive ID from search_archive results (archiveId field)
`overlap_sqkm`	Yes	Overlap area in sq km from search results (overlapSqkm)
`price_per_sqkm_usd`	Yes	Price per sq km from search results (priceForOneSquareKm)
`price_full_scene_usd`	Yes	Full scene price from search results (priceFullScene)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 10, 2026

TDQS

A4.2/5.0

Behavior4/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It explains the return value (quote_id valid 15 minutes, human-readable summary) and the required confirmation workflow. It does not, however, state whether the quote has server-side side effects or what happens on expiration, but what it does disclose is valuable and goes beyond basic schema information.

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?

The description is exceptionally concise—two sentences that are front-loaded with the core purpose. Every clause provides critical information: the binding nature, return format, expiration, and the required confirmation step. No word is wasted.

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 tool with five parameters, no output schema, and no annotations, the description covers the essential context: what the tool returns, how long it's valid, and the required follow-up action. It does not explain parameter inputs, but the schema fully covers those. The description is sufficient for an agent to use the tool correctly, though it could mention error conditions or non-binding alternatives.

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?

All five parameters are fully described in the input schema, so the schema provides 100% coverage. The description adds no additional parameter-specific meaning beyond what the schema already conveys, which meets the baseline expectation for this dimension.

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's function with a specific verb ('Generate') and resource ('binding quote for an archive order'). It distinguishes itself from the sibling execute_archive_order by indicating the quote must be confirmed before execution, making its role in the workflow unambiguous.

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?

The description provides clear usage context: generate a quote, present it to the user, and wait for explicit confirmation before calling execute_archive_order. While it implies this is a pre-execution step, it does not explicitly mention when to use this instead of the similarly named estimate_archive_price tool, though 'binding' hints at the distinction.

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