Skip to main content
Glama
Sign In

Gillby

by io.github.OneWave-AI
OverviewDiscussionsAdmin

Find marinas

find_marinas
Read-onlyIdempotent

Search published marinas by name or west,south,east,north bbox. Follow with get_poi_details using the returned ID for contacts, parking counts, permits and closure notices. Verify access and operating details with the facility. Bridge data is published, not a live clearance calculation.

Units: ft, kt, s, F, mi; directions FROM. Returns data and source/freshness metadata.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "find_marinas"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the read-only, open-world, idempotent, non-destructive profile. The description adds useful behavioral context beyond that: only published marinas are returned, data is not a live clearance calculation, verification with the facility is advised, and source/freshness metadata is included.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded and the sentence order is mostly logical, but the sentence 'Bridge data is published, not a live clearance calculation' appears irrelevant to marinas and does not earn its place. The units and metadata sentences are compact but the overall text contains one clear distractor.

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 no output schema and rich annotations, the description is nearly complete: it explains the search inputs, follow-up retrieval with get_poi_details, verification needs, data freshness caveats, units, and return metadata. The main gap is the undocumented limit parameter and nested query object, though the schema provides defaults and type constraints.

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 0%, so the description must compensate. It documents the 'q' search by name and the bbox format as west,south,east,north, but it omits the limit parameter entirely and does not explain the nested query object structure.

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 states a specific verb and resource: 'Search published marinas by name or west,south,east,north bbox.' It clearly distinguishes this tool from sibling find_* tools by resource type and supplies scope (published only).

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?

It gives follow-up workflow guidance ('Follow with get_poi_details') and a verification caution, but does not explicitly say when to use this tool instead of alternatives like search_pois or find_fuel_docks. Usage is implied rather than stated.

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

All Gillby toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources