Skip to main content
Glama

船舶検出

analyze_ship

Sentinel-1 SAR画像(GRD)から船舶を検出します。 ■ 入力: 以下のどちらかで解析対象を指定。 (A) scene_id(Sentinel-1 GRDのシーンID)。ASF Search(https://search.asf.alaska.edu/#/)でFile TypeをGRDに絞って検索可能。 (B) polygon(WKT)+ date(基準日 YYYY-MM-DD)。該当範囲・基準日に近い1シーンを自動選定。date_direction で選択方向を指定可能。 ■ 処理: GPU推論による物体検出。推定所要時間は約30分。 ■ 出力: 検出された船舶のポリゴンを含むGeoJSON。 ■ フロー: ジョブ投入後 job_id が返される。check_job_status でポーリングし、completed 後に get_job_result で結果取得。 ■ 実行前に preview_analysis で解析範囲と消費クレジットを確認し、ユーザーの承認を得てください。ジョブは投入後にキャンセルできません。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateNo基準日(YYYY-MM-DD)。polygon 指定時に必須。この日付に近いシーンを自動選定
polygonNoWKT形式ポリゴン(例: POLYGON((139.7 35.6, 139.8 35.6, 139.8 35.7, 139.7 35.7, 139.7 35.6)))。date とセットで指定すると該当範囲の1シーンを自動選定。scene_id 指定時は不要
scene_idNoSentinel-1 GRDのシーンID(例: S1A_IW_GRDH_1SDV_20240101T...)。ASF Search で検索可能。polygon + date を指定する場合は不要
satellite_idYes衛星ID。現在 sentinel-1 のみ対応
date_directionNo基準日に対するシーン選択方向(before/after/nearest)。polygon + date 指定時のみ有効。省略時は nearest
orbit_directionNo軌道方向(ascending / descending)。polygon + date 指定時のみ有効。省略時は自動判定

TDQS

A4.9/5.0
Behavior5/5

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

在annotations只表达非只读、非破坏性的基础上,描述补充了大量关键行为:GPU推理、约30分钟耗时、返回job_id的异步模式、输出GeoJSON、作业提交后不可取消、执行前需用户批准。这些信息远超结构化标注的承载量,充分披露了工具的副作用和时间成本。

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?

采用■分段结构将输入、处理、输出、流程、前置条件拆分为独立模块,信息密度高且无冗余。对异步作业型工具而言,每一条内容(输入A/B、耗时、取消限制、批准要求)都是调用决策所需的最小必要信息,长度与复杂度匹配。

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?

工具涉及6个参数、异步作业、需事先批准、结果需二次获取,复杂度高。描述涵盖了输入二选一约束、处理时长、输出格式、后续轮询与取结果步骤、取消限制和前置批准要求,各环节闭环。虽然缺少输出schema,但描述已声明返回的是含船舶多边形的GeoJSON,对智能体正确调用和结果预期无缺口。

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

Parameters4/5

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

Schema的6个参数覆盖率100%,但描述额外传达了schema无法直接表达的语义——scene_id与polygon+date的互斥分组关系(A/B模式)、参数之间的依赖条件(polygon需与date成对、date_direction仅在polygon+date模式下生效)。还提供了ASF Search检索入口辅助查找scene_id,增强了参数的实用语义。

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?

描述以特定动词「検出」明确了从Sentinel-1 SAR画像(GRD)检测船舶的功能,资源、数据源和处理方式都清晰无歧义。与兄弟工具analyze_oilslick、analyze_newbuilding等在分析主题上天然区分,工具边界明确。

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?

描述明确给出了两种输入方式(scene_id路径与polygon+date路径)的适用场景,并指定了何时必须搭配date、何时省略。还显式说明了执行顺序——先用preview_analysis获取用户批准,再提交作业,用check_job_status轮询、get_job_result取结果,以及与兄弟工具的调用衔接关系完整。

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.6/5.0
Disambiguation5/5

Each analysis tool targets a distinct detection type (buildings disappearing, new buildings, oil slick, ships, surface changes), and job management tools have clear separate roles (status, result, list). The polygon drawing and preview tools are also uniquely scoped.

Naming Consistency5/5

All tools follow a consistent verb_noun pattern: analyze_* for detections, check_job_status / get_job_result / list_jobs for job operations, and open_polygon_draw / preview_analysis for supporting actions. No mixed conventions or vague verbs.

Tool Count5/5

Ten tools cover the full workflow without redundancy: five analysis types, three job management utilities, one drawing helper, and one preview gate. This is well-scoped for a satellite analysis server.

Completeness5/5

The workflow is complete: preview to approve, submit analysis, poll status, retrieve results, list past jobs, and draw polygons. The domain covers the major SAR-based detection needs and includes explicit guidance for handling long-running jobs.

Resources