Skip to main content
Glama
loosephoto

space-finder-mcp

by loosephoto
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

eodashboard_detail

Get detailed info for any EO Dashboard dataset including satellite, sensor, description, and reference links, plus a thumbnail image link for chat display.

Instructions

EO Dashboard の1つのデータセットの詳細（衛星・センサー・説明・参照リンク・画像）を返す。

例:「NO2データセットの詳細」「EO Dashboardの海面水温の情報」
content に表示用サマリ＋サムネイル画像(インライン)、structuredContent に JSON を返す。

インライン画像を表示できないハーネス（CLI系・Android系の codex / opencode など）向けに、
画像本体より前に「🖼️ [サムネイル画像を開く: …](URL)」というアイコン付きリンクを必ず出します
（同じURLを structuredContent.image_url にも入れます）。
回答時はこのリンクをそのまま提示してください（画像が描画されない環境では唯一の導線）。

Args:
    identifier: コレクションIDまたは名前（例 "N1_NO2", "NO2_daily", "sea_ice"）。
                大まかな名前でも探す。
    show_image: サムネイルをチャットにインライン表示するか（既定 True）。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
identifierYes
show_imageNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.25.2

TDQS

A4.8/5.0
Behavior5/5

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

With no annotations, the description carries the full burden. It transparently discloses output format (content with summary + inline thumbnail, structuredContent JSON), the always-emitted fallback link for non-image harnesses, that show_image controls inline rendering, and that identifier accepts rough names. This is rich behavioral context beyond the schema.

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 organized as purpose → examples → output behavior → args. Each sentence adds needed information; the link-handling instruction is verbose but critical because it directly instructs the agent on response presentation. No fluff.

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

Completeness5/5

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

Given the tool's simplicity (2 simple params), the description covers invocation, parameter semantics, and output handling, including a specific field name (structuredContent.image_url). It would benefit from stating error behavior or a structuredContent schema, but for an agent deciding to call, it is sufficient.

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 has 0% description coverage, so the description's Args section is essential. It explains identifier as collection ID or name with examples ('N1_NO2', 'sea_ice') and notes fuzzy matching ('大まかな名前でも探す'), and defines show_image's default and role. This fully compensates for the empty schema.

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?

Description states 'EO Dashboard の1つのデータセットの詳細（衛星・センサー・説明・参照リンク・画像）を返す' – a specific verb (返す) and resource (one dataset's details). This clearly distinguishes from collection-listing siblings like eodashboard_collections.

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?

Provides concrete example queries ('NO2データセットの詳細', 'EO Dashboardの海面水温の情報') that signal when to invoke, and scopes itself to a single dataset with '1つの'. It lacks explicit exclusion of alternatives (e.g., eodashboard_collections for lists), so it stops short of full when-not guidance.

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