Skip to main content
Glama
Sign In
subsea-robotics-survey

subsea-robotics-survey

by tudadada
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

auv_multibeam_survey_coverage

Calculate AUV multibeam bathymetric coverage rates, line spacing, and carbon abatement versus DP2 support vessels to plan efficient seabed surveys.

Instructions

Calculates autonomous underwater vehicle (AUV) multibeam sonar bathymetric coverage rates (km2/hr and km2/day), line spacing, and carbon abatement metrics versus conventional DP2 support vessels.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "altitude_meters": "<altitude_meters>"
    },
    "name": "auv_multibeam_survey_coverage"
  }
}

Input Schema

NameRequiredDescriptionDefault
speed_knotsNoCruising speed in knots. Default: 3.5 knots.
altitude_metersYesFlying altitude of the AUV above the seabed in meters (e.g. 20.0, 40.0).
swath_angle_degNoMultibeam total swath aperture angle in degrees. Default: 120.0°.
line_overlap_percentNoSurvey track overlap percentage for bathymetric QA/QC. Default: 20.0%.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are provided, so the description carries full burden. It does disclose the computed output metrics and their units, which gives the agent a picture of the result, but it omits any statement of assumptions, validity ranges for altitude/speed, or that this is a pure, side-effect-free calculation.

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 single front-loaded sentence with no filler; every clause (coverage rates, line spacing, carbon abatement comparison) carries information the agent needs to judge relevance.

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?

With a 100%-covered schema and no output schema, the description covers what the tool computes and the main output metrics. It stops short of stating modeling assumptions or limits (e.g., valid altitude/overlap ranges, or that carbon figures are estimates versus a DP2 baseline), which would matter for a physics/emissions calculator.

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 100%, so all four parameters (including defaults for speed, swath angle, overlap) are already documented in the schema. The description adds no syntax, units, or constraints beyond what the schema provides, so the baseline 3 is appropriate.

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 ('Calculates') and a precise resource ('AUV multibeam sonar bathymetric coverage rates, line spacing, carbon abatement metrics'), with the output units named (km2/hr, km2/day). The sibling tools are entirely different domains (torque, cathodic protection, bolting), so no sibling confusion arises.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use / when-not-to-use statement and no named alternatives. Usage is implied by the framing ('versus conventional DP2 support vessels'), which signals a comparative survey-planning context, but the agent must infer that on its own.

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