Skip to main content
Glama
Sign In

Gillby

by io.github.OneWave-AI
OverviewDiscussionsAdmin

Get coastal place

get_poi
Read-onlyIdempotent

Look up a published coastal POI by its exact ID. Use get_poi_details with this ID for supported facility parking, contacts and source facts; this listing does not calculate live bridge clearance.

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"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the bar is low. The description adds real context beyond them: a negative capability (no live bridge clearance calculation), the unit conventions (ft, kt, s, F, mi), the FROM direction convention, and that source/freshness metadata is returned.

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?

Purpose is front-loaded in the first sentence, routing guidance second, and the units/return line last where it belongs. Dense but every sentence carries information; the units line is terse enough not to feel padded.

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, the description does step in to say what comes back ('data and source/freshness metadata') and fixes units and direction conventions. For a single-ID lookup that is nearly sufficient; only the ID provenance/format is left implicit.

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 carry the load, and it does add one meaningful fact: the identifier must be an 'exact ID', implying no fuzzy matching. It still says nothing about the ID format, length limits, or where IDs come from, which a 0%-coverage nested parameter would benefit from.

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 and resource ('Look up a published coastal POI') with a scoping qualifier ('by its exact ID') that clearly separates it from search_pois (lookup vs query) and get_poi_details (summary vs details). An agent can route without opening any schema.

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?

Explicitly names the alternative get_poi_details and the condition that selects it ('for supported facility parking, contacts and source facts'), and carves out a when-not ('does not calculate live bridge clearance'). It does not explain how to obtain a valid ID or relate to search_pois, so it falls short of full 5-level coverage.

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