SkyFi MCP Server

explore_open_data

Browse open satellite data on SkyFi. Filter by provider or region to locate free datasets for any area.

Instructions

Browse freely available datasets on SkyFi, filterable by provider and region. Use this when the user asks about free or open satellite data.

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": "explore_open_data"
  }
}

Input Schema

Name	Required	Description
`page`	No
`limit`	No
`region`	No	Filter by region name
`provider`	No	Filter by data provider name

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 10, 2026

TDQS

A3.7/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 states the action ('browse') and filtering capabilities but does not disclose pagination behavior, return format, or whether the operation is read-only. The schema indicates page and limit parameters, but the description adds no behavioral nuance beyond the obvious.

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 concise, front-loaded sentences. The first defines the tool's function, the second gives usage context. No wasted words or redundant restatements of the schema.

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

Completeness3/5

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

With no output schema and no annotations, the description leaves the return value implicit. It correctly identifies the tool's purpose and filter options, but does not explain what the response looks like or that pagination is possible. This is a minor gap for a simple browsing tool, but could be more informative.

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 50% (region and provider have descriptions). The tool description mentions both provider and region as filters, adding slight context, but page and limit are left undefined in both schema and description. For a list-browsing tool, page/limit are self-explanatory, so this is adequate but not exceptional.

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 ('Browse') and resource ('freely available datasets on SkyFi'), and clarifies the distinction from siblings by emphasizing 'free or open' data. This clearly differentiates it from tools like search_archive or purchase-related tools.

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 an explicit usage directive: 'Use this when the user asks about free or open satellite data.' This gives a clear trigger condition, though it does not explicitly name alternative tools or exclusion criteria, which prevents a perfect score.

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