Skip to main content
Glama
Sign In

Gillby

by io.github.OneWave-AI
OverviewDiscussionsAdmin

Find fuel docks

find_fuel_docks
Read-onlyIdempotent

Search published fuel docks 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_fuel_docks"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive, open-world behavior. The description adds genuinely new context beyond them: the data is published rather than a live clearance calculation, the facility should be contacted to verify, and the response includes source/freshness metadata.

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

Conciseness4/5

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

Front-loaded with the core action and scoping, with the follow-up and caveats packed into short sentences. The trailing 'Units' line is somewhat generic API boilerplate that adds little for this particular tool, slightly diluting conciseness.

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 search tool with no output schema, the description covers purpose, next-step tool, data-freshness caveat, and that source/freshness metadata is returned. The only notable gap is documentation of the limit parameter and nested query structure.

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 carries the burden. It explains the two meaningful inputs (name query and west,south,east,north bbox format), which is useful, but omits the 'limit' parameter entirely and does not explain the nested 'query' wrapper.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Search published fuel docks') plus the two search modes (name or west,south,east,north bbox), so the agent knows exactly what the tool returns. It does not explicitly contrast itself with fuel-relevant siblings like find_marinas, so it stops short of a 5.

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 a clear follow-up workflow ('Follow with get_poi_details using the returned ID for contacts, parking counts, permits and closure notices') and a caveat to verify details with the facility. It does not state when to prefer this over sibling find_* tools, so it is clear context but not full alternative routing.

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