Diver Atlas

find_trips

Read-only

Areas with diving open or limited in a calendar month (1–12 or month name). Optional species keyword filters species windows.

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": {
      "month": "<month>"
    },
    "name": "find_trips"
  }
}

Input Schema

Name	Required	Description	Default
`month`	Yes
`species`	No

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 4, 2026

TDQS

B3.1/5.0

Behavior3/5

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

Annotations already declare this as a safe, read-only, closed-world operation. The description adds useful context that results are areas with diving status 'open or limited' for a month and that species narrows windows, but it does not explain response shape, ordering, or what 'limited' means.

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 a single compact sentence with no filler, and the core constraint (calendar month) is front-loaded. It is dense and would be clearer if led by a verb, but it is appropriately sized for a two-parameter tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple read-only lookup with no output schema and empty parameter descriptions, the description covers the essential inputs and intended result type. However, it leaves gaps around output structure, the meaning of 'limited', and the boundary against sibling suitability and season tools.

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 description coverage is 0%, so the description must carry parameter meaning. It does so by explaining that month accepts 1–12 or a month name and that species is an optional keyword filter for species windows; the species semantics remain somewhat vague, preventing a 5.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description identifies the returned data (areas with diving open or limited in a given month) and the optional species filter, but it is a noun phrase without an action verb. It also never explains the relationship between the tool name find_trips and the 'areas' result, and it does not distinguish itself from sibling suitability tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance and no mention of alternatives such as check_suitability, batch_check_suitability, or get_area_seasons. The description only states what inputs exist, leaving the agent to infer the decision context.

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

All Diver Atlas 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?