Skip to main content
Glama
Sign In

Headed In: Florida trips, water and weather

by com.headedin
OverviewDiscussionsAdmin

Florida Passport stamps

florida_passport
Read-onlyIdempotent

The Florida Passport stamp book (55 stamps on 11 region pages: Mile Marker 0, Coral Castle, Weeki Wachee mermaids, a spring swim, Skunk Ape HQ, the time zone line, free OJ at a Welcome Center...). Each stamp is earned only by standing there with the free Headed Back app. Give a position for the closest stamps, a page (road, bay, sarasota, southwest, miami, keys, space, central, nature, northeast, panhandle) or a name. Use it for Florida bucket lists, road-trip stops, or 'what should we not miss'.

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

Input Schema

NameRequiredDescriptionDefault
latNoLatitude of where the person is or will be
lonNoLongitude
nameNoOr part of a stamp or place name, e.g. Coral Castle, Ybor
pageNoA region page id or part of its name, e.g. keys, panhandle, Space Coast
limitNoHow many (default 8, a whole page 10, up to 20)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, and open-world behavior. The description adds meaningful context beyond that: stamps are earned only by physically standing at the location with the free Headed Back app, which is important behavioral context for an agent.

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?

The description is reasonably sized and most sentences earn their place by conveying scope, mechanics, and usage. The long parenthetical stamp examples are somewhat decorative but still help convey the tool's domain and are front-loaded enough to orient the reader.

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?

Given the annotations and the fully described parameter schema, the description gives an agent enough to call the tool correctly. It does not explain the return shape, but with no output schema and a simple retrieval purpose, that omission is minor.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds value by explaining the alternative query modes and listing all 11 region page IDs, which the schema does not fully enumerate. It also clarifies that position input is for finding the closest stamps.

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?

The description clearly identifies a specific resource: the Florida Passport stamp book with 55 stamps across 11 region pages. It implies retrieval by position, page, or name, which is understandable, though it never explicitly states 'returns stamps' and does not directly distinguish itself from broader siblings like find_places.

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?

It gives clear usage contexts such as Florida bucket lists, road-trip stops, and 'what should we not miss,' and explains the three query modes. It does not name alternatives or say when not to use this tool, so it stops short of full routing guidance.

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

All Headed In: Florida trips, water and weather 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