Skip to main content
Glama
Sign In

Gillby

by io.github.OneWave-AI
OverviewDiscussionsAdmin

Get facility details

get_poi_details
Read-onlyIdempotent

Read source-linked details for a published Florida boat ramp, marina, fuel dock or waterfront restaurant by exact POI ID returned by a place search. Includes contact details, parking trailer/car/accessible space counts where published, hours, fees, slips, amenities and per-field sources/dates. Launch parking includes 84 collected FWC records and checked operator guidance at selected facilities; launch:notice facts may describe construction or closure and take priority over routine hours/rates. Published capacity is not live availability. Preserve unknown values, source dates and conflicting records. Does not establish current ramp reopening, trailer permission, dock access, live fuel prices or navigable depth. California directory IDs use list_california_facilities; use get_parking_guides for checked California parking guidance.

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

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": {
      "query": "<query>"
    },
    "name": "get_poi_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already cover readOnly/idempotent/openWorld, but the description adds substantial behavior: the returned field set, per-field sources/dates, that launch:notice facts override routine hours/rates, that published capacity is not live availability, that unknown values and conflicting records must be preserved, and unit conventions. None of this is recoverable from the annotations.

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?

Dense but front-loaded: the primary action and ID source come first, then inclusions, caveats, exclusions, and units. Every clause carries information, though the middle section enumerates many fields and specific record counts that could be tightened.

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?

With no output schema, the description steps in to enumerate the returned content (contacts, parking counts, hours, fees, slips, amenities, per-field sources, freshness metadata) and units. Combined with the explicit negative guarantees and sibling routing, an agent has everything needed to call and interpret this read tool.

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% for the single nested query.id parameter, so the description must carry the load—and it does add meaning by specifying the ID is an exact POI ID obtained from a place search (not a fuzzy lookup). However it offers no format constraints or examples to compensate for the undocumented schema field, so this is adequate but incomplete.

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 (Read) plus the exact resource (source-linked details for a published Florida boat ramp, marina, fuel dock or waterfront restaurant) keyed by a POI ID from a place search. It also distinguishes itself from get_poi, search_pois, and list_california_facilities by naming the ID origin and the California-directory boundary, so an agent can route to it without opening another schema.

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?

Explicitly says the ID comes from a place search and that California directory IDs must go to list_california_facilities, with checked California parking guidance routed to get_parking_guides. It also lists clear when-not conditions (does not establish reopening, trailer permission, dock access, live fuel prices, or navigable depth).

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