Skip to main content
Glama
Sign In
space-finder-mcp

space-finder-mcp

by loosephoto
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

inpe_search

Search Brazilian INPE satellite imagery (CBERS, Amazonia-1, GOES) via STAC by collection, bounding box, date range, and cloud cover; no authentication required.

Instructions

ブラジルINPEの衛星画像（CBERS・Amazonia-1・GOES等）をSTACで検索する（認証不要）。

例:「ブラジルのCBERS衛星画像」「サンパウロ周辺の最近の衛星画像」

Args: collection: STAC コレクションID（既定 "CB4-WFI-L4-SR-1"）。inpe_collections で確認可。 bbox: 空間範囲（"lon_min,lat_min,lon_max,lat_max"）。 datetime: 時間範囲（"YYYY-MM-DD" または "start/end"）。省略で最新。 max_cloud_cover: 雲量上限（%）（eo:cloud_cover を持つ場合）。 limit: 返す件数（既定 5、最大 10）。

Input Schema

NameRequiredDescriptionDefault
bboxNo
limitNo
datetimeNo
collectionNoCB4-WFI-L4-SR-1
max_cloud_coverNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed15 schema fields changedv0.41.4
    • removedInput schema / properties / bbox / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
    • removedInput schema / properties / bbox / default
      Removed value: -null
    • removedInput schema / properties / bbox / title
      Removed value: -"Bbox"
    • addedInput schema / properties / bbox / type
      Added value: +[
+  "string",
+  "null"
+]
    • removedInput schema / properties / collection / title
      Removed value: -"Collection"
    • removedInput schema / properties / datetime / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
    • removedInput schema / properties / datetime / default
      Removed value: -null
    • removedInput schema / properties / datetime / title
      Removed value: -"Datetime"
    • addedInput schema / properties / datetime / type
      Added value: +[
+  "string",
+  "null"
+]
    • removedInput schema / properties / limit / title
      Removed value: -"Limit"
    • removedInput schema / properties / max_cloud_cover / anyOf
      Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]
    • removedInput schema / properties / max_cloud_cover / default
      Removed value: -null
    • removedInput schema / properties / max_cloud_cover / title
      Removed value: -"Max Cloud Cover"
    • addedInput schema / properties / max_cloud_cover / type
      Added value: +[
+  "number",
+  "null"
+]
    • removedInput schema / title
      Removed value: -"inpe_searchArguments"
  2. Addedv0.25.2

TDQS

A4.2/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral burden, and it makes a genuinely useful disclosure: no authentication is required, and the result cap is 10. It says nothing about read-only guarantees, what an item/asset looks like in the response, pagination, or failure modes for invalid collection IDs.

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 one-line purpose, then two illustrative examples, then compact per-parameter notes. Every line contributes something, though the Args block necessarily repeats the schema defaults to be usable.

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 five-parameter, no-annotation, no-output-schema search tool, the description covers all inputs and the auth posture. The remaining gap is what the results actually contain (items, assets, download URLs) and how to page beyond the hard limit of 10.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the Args block is the only documentation and it fully compensates: bbox as 'lon_min,lat_min,lon_max,lat_max', datetime as 'YYYY-MM-DD' or 'start/end' with latest-when-omitted behavior, collection default, limit default 5 / max 10, and the caveat that max_cloud_cover applies only when eo:cloud_cover exists.

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: search Brazilian INPE satellite imagery (CBERS, Amazonia-1, GOES) via STAC, plus the notable constraint '認証不要'. The agency scoping distinguishes it from the many generic STAC siblings, and it points to inpe_collections for valid collection IDs.

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?

Concrete example queries ('ブラジルのCBERS衛星画像', 'サンパウロ周辺の最近の衛星画像') make the intended usage immediately clear, and it routes to inpe_collections for collection discovery. It does not say when to prefer stac_search or another agency's search tool over this one, so there is no explicit exclusion.

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

Deploy Server

Other Tools