Headed In: Florida trips, water and weather

Draft a float plan

draft_float_plan

Read-onlyIdempotent

For a boat trip: a link that opens Headed In's Float plan with the route, crew, hours, leave time, safety gear and a note already filled in. The boater checks it and starts the trip in the app themselves.

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

Input Schema

Name	Required	Description
`crew`	No	People aboard
`gear`	No
`note`	No	Anything else for their people, 140 characters
`hours`	No	Hours out, in half hours
`route`	No	Where they're going, e.g. John's Pass to Egmont Key (140 characters)
`leave_in_hours`	No	0 now, 1 or 2 hours from now, 12 tomorrow

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 22, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and open-world behavior. The description adds important context beyond them: the output is a link with pre-filled fields, and the boater must review and start the trip themselves, meaning the tool does not initiate the trip.

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

Conciseness5/5

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

Two sentences, both front-loaded and purposeful. The first explains what is produced, and the second clarifies the user's required follow-up action with no wasted wording.

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 annotations covering safety and idempotency, and the schema covering parameter semantics, the description supplies the missing output behavior (a link) and user flow. It does not cover link expiration or app requirements, but it is otherwise complete for correct invocation.

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 83%, so the schema already documents nearly all parameters. The description enumerates route, crew, hours, leave time, safety gear, and note as pre-filled fields, which reinforces their role but does not add format or constraint details beyond the schema.

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 states that the tool produces a link that opens a pre-filled float plan with specific fields. It distinguishes the action from actually starting the trip by noting the boater checks it and starts in the app themselves, though it does not name a sibling alternative.

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?

The phrase 'For a boat trip' gives context, and the note that the boater completes the process in the app implies this is a preparation step. However, it does not explicitly state when to use this versus alternatives like open_plan_in_app or what prerequisites exist.

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?