SkyFi MCP Server

execute_tasking_order

Destructive

Confirm and place a satellite imaging tasking order using a verified quote. Requires explicit user approval to execute, preventing unauthorized orders.

Instructions

Place a tasking order using a confirmed quote. Preconditions: (1) valid quote_id from quote_tasking_order, (2) explicit user confirmation, (3) idempotency_key (UUID). Do NOT call this tool autonomously — always wait for user confirmation.

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": {
      "aoi": "<aoi>",
      "product_type": "<product_type>",
      "resolution": "<resolution>",
      "window_start": "<window_start>",
      "window_end": "<window_end>",
      "user_confirmed": "<user_confirmed>"
    },
    "name": "execute_tasking_order"
  }
}

Input Schema

Name	Required	Description
`aoi`	Yes	GeoJSON Polygon for the tasking area
`label`	No	Optional label for this order
`resolution`	Yes	Required image resolution
`window_end`	Yes	Capture window end (ISO 8601)
`product_type`	Yes	Satellite product type
`window_start`	Yes	Capture window start (ISO 8601)
`user_confirmed`	Yes	Must be true — confirms the user has reviewed feasibility and pricing and approved
`max_cloud_cover_pct`	No	Maximum acceptable cloud cover %

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 10, 2026

TDQS

A4.1/5.0

Behavior4/5

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

The destructiveHint annotation already signals mutating behavior. The description adds meaningful context: it must not be called autonomously, requires user confirmation, and needs an idempotency key. This goes beyond the annotation, though it doesn't cover failure modes or return behavior.

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 two sentences: the first states the purpose, the second lists preconditions and a warning. It is front-loaded, concise, and every sentence carries critical information without redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a complex tool with 8 parameters, the description omits that quote_id and idempotency_key are not in the schema, creating a significant invocation gap. It also does not clarify the order lifecycle or confirmation details. The schema fills in parameter semantics, but the mismatch hurts overall completeness.

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?

Although schema coverage is 100%, the description references quote_id and idempotency_key as essential preconditions, but these fields are absent from the input schema. This mismatch confuses parameter understanding and the description does not map actual schema parameters to the preconditions, reducing its added value.

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 uses a specific verb 'Place' with the resource 'tasking order' and clarifies the requirement for a confirmed quote. This distinguishes it from sibling tools like execute_archive_order and quote_tasking_order, making the purpose unambiguous.

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?

The description explicitly lists preconditions: valid quote_id from quote_tasking_order, explicit user confirmation, and idempotency_key. It also provides a clear exclusion: 'Do NOT call this tool autonomously — always wait for user confirmation.' This is strong when/when-not guidance.

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