Skip to main content
Glama

Datalastic

by io.github.pipeworx-io
OverviewAdmin

Datalastic Vessels In Radius

datalastic_vessels_in_radius
Read-onlyIdempotent

Find vessels within nm of a lat/lon — live AIS positions of all ships near a point. Returns each ship's name, IMO, MMSI, position, speed, course, destination and type. Example: datalastic_vessels_in_radius({ lat: 51.95, lon: 1.28, radius: 20, _apiKey: "your-key" })

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
latYesCenter latitude in decimal degrees, e.g. 51.95
lonYesCenter longitude in decimal degrees, e.g. 1.28
radiusYesSearch radius in nautical miles, e.g. 20
_apiKeyYesDatalastic API key (get one with a trial at datalastic.com)

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "_apiKey": "your-datalastic-api-key",
+    "lat": 51.95,
+    "lon": 1.28,
+    "radius": 20
+  }
+]
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already mark it as read-only, idempotent, and non-destructive. The description adds value by disclosing that it returns live AIS positions, the specific fields (name, IMO, MMSI, position, speed, course, destination, type), and the need for an API key ('_apiKey'), which is a behavioral trait not covered by annotations.

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 two sentences plus an example, achieving high information density with zero waste. The first sentence states the core purpose, the second lists return fields, and the example anchors the usage. It is well-front-loaded and easy to parse.

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 read-only, idempotent tool with no output schema, the description adequately explains what it does, what it returns, and how to call it. It does not mention potential radius limits or error handling, but these are not essential for basic usage. The presence of a sibling tool for specific vessels could be referenced, but the description stands on its own.

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?

The input schema provides 100% coverage with clear descriptions for all four parameters. The description adds an example call that demonstrates the parameter order and values, which is modest additional value beyond the schema, but does not introduce new semantic information for any parameter.

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?

The description begins with a specific verb 'Find' and clearly states the resource: 'vessels within <radius> nm of a lat/lon'. It distinguishes itself from sibling 'datalastic_vessel' by emphasizing 'all ships near a point' and listing return fields, making the tool's scope unmistakable.

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?

The description clearly implies the use case: spatial search for all vessels near a point with live AIS positions. It does not explicitly mention alternatives or exclusions, but the contrast with the singular 'datalastic_vessel' sibling is implicit. The example call provides concrete usage context.

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

All Datalastic toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources