Headed In: Florida trips, water and weather

Florida town names and weird spots

florida_stories

Read-onlyIdempotent

Short true stories pinned all over Florida, closest first: Name game (why a town is called what it is: Pass-a-Grille, Kissimmee, Key West...) and Weird Florida (Koreshan hollow-earth camp, the world's smallest police station, Robert the Doll...). Each has a teaser, the spot and a map link; the whole story opens in the Headed Back app at the place. Great as road-trip stops.

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

Input Schema

Name	Required	Description
`lat`	No	Latitude of where the person is or will be
`lon`	No	Longitude
`kind`	No	Only one kind; leave out for both
`limit`	No	How many to return

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 22, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, open-world), so the description earns credit for what it adds: proximity-based ordering, the per-item payload (teaser, spot, map link), and the fact that the full story opens in the Headed Back app at that place — a real deep-link behavior an agent would otherwise not know.

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 front-loaded first clause states the resource and sort order immediately; the example enumerations are colorful but do real work by defining the two content kinds. It is slightly parenthetical-heavy but nothing is filler.

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 usefully describes the returned item shape (teaser, spot, map link) and the app hand-off. The remaining gap is behavior when lat/lon are absent, since zero parameters are required, which leaves the default result set ambiguous.

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 coverage is 100% including the enum values, so the schema carries the parameter burden and the baseline is 3. The description adds only implicit semantics — 'closest first' hints that lat/lon drive ordering — but never says what happens if they are omitted, despite no parameters being required.

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 names a concrete resource (short true stories about Florida town names and weird spots) and a scope ('pinned all over Florida, closest first'), plus two named content categories. It stops short of differentiating itself from the plausible sibling story_trails, so the agent still has to guess when the two overlap.

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?

Usage is only implied: 'closest first' and 'Great as road-trip stops' suggest a location-driven browse use case, but there is no explicit when-to-use or when-not-to-use statement and no mention of the story_trails sibling as an alternative.

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 tools Inspect

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

Need Help?