Skip to main content
Glama
Sign In
loosephoto

space-finder-mcp

by loosephoto
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

roscosmos_search

Search Roscosmos weather satellite imagery from Elektro-L, Arktika-M, and Meteor-M by collection and date to retrieve available images without authentication.

Instructions

Roscosmos の気象衛星画像（Elektro-L・Arktika-M・Meteor-M）を検索する（認証不要）。

例:「ロシアの静止気象衛星エレクトロLの全球画像」「今日のMeteor-Mモザイク」

Args: collection: コレクションのパス（例 "Electro-L/MSU-GS/L2_RGB_VIS_IR"、 "MM/MSU-MR/L3MD"、"EL_ARCM/MSU-GS/L3BT9"、"Arctic-M/MSU-GS-A/L2_RGB_VIS_IR"）。 roscosmos_collections で確認できます。未知のパスは候補を返して停止します。 date: 日付（"YYYY-MM-DD"・UTC）。省略でデータがある最新日。 limit: 返す件数（既定 3、最大 8）。 lookback: 日付省略時にさかのぼる最大日数（既定 7、最大 30）。

Input Schema

NameRequiredDescriptionDefault
dateNo
limitNo
lookbackNo
collectionNoElectro-L/MSU-GS/L2_RGB_VIS_IR

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changedv0.41.4
    • removedInput schema / properties / collection / title
      Removed value: -"Collection"
    • removedInput schema / properties / date / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
    • removedInput schema / properties / date / default
      Removed value: -null
    • removedInput schema / properties / date / title
      Removed value: -"Date"
    • addedInput schema / properties / date / type
      Added value: +[
+  "string",
+  "null"
+]
    • removedInput schema / properties / limit / title
      Removed value: -"Limit"
    • removedInput schema / properties / lookback / title
      Removed value: -"Lookback"
    • removedInput schema / title
      Removed value: -"roscosmos_searchArguments"
  2. Addedv0.39.0

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden and does well: it discloses that authentication is not required, that unknown collection paths return candidates and stop, and that date omission uses the latest available date. It still omits rate-limit behavior and what a result actually contains.

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?

Front-loaded with purpose and useful examples, then compact Args. There is no filler, and the examples help an agent map natural-language requests to the correct collection.

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?

Invocation details are strong: auth, unknown-path behavior, defaults, and limits are all covered. However, with no output schema, the description never explains whether results are image URLs, scene metadata, or a list of items, so the agent cannot predict the return shape.

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 coverage is 0%, so the description must carry all parameter meaning, and it does: collection paths are given with concrete examples and a pointer to roscosmos_collections; date specifies YYYY-MM-DD UTC and default behavior; limit and lookback state defaults and maximums.

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 Roscosmos meteorological satellite imagery for Elektro-L, Arktika-M, and Meteor-M, and notes that authentication is not required. It also names roscosmos_collections as the place to verify collection paths, which distinguishes this search tool from the collection-listing sibling.

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?

Gives concrete query examples and points to roscosmos_collections for valid collection paths, plus fallback behavior for unknown paths. It does not explicitly say when not to use this tool versus other imagery-search siblings, so it stops short of full alternative routing.

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