Skip to main content
Glama
Sign In

Esoru by resortlife.travel

by travel.resortlife
OverviewDiscussionsAdmin

When and where to see marine life

when_to_see
Read-onlyIdempotent

Where and in which months to see an animal in the Maldives: manta rays, whale sharks, turtles, hammerheads and others. Gives the species' season, the sites that list it with each site's stated season, a month-by-month count, and the nearest stays to each site by straight line. With a month, sites stated as out of season are left out and counted. Never promises a sighting.

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": {
      "species": "<species>"
    },
    "name": "when_to_see"
  }
}

Input Schema

NameRequiredDescriptionDefault
atollNoAtoll name, partial match — e.g. "Baa", "South Ari".
limitNoMaximum sites (1-30).
monthNoThe month of travel.
speciesYesThe animal, e.g. "manta", "whale shark", "hawksbill turtle".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already declare read-only, idempotent, non-destructive behavior, and the description goes well beyond them: it discloses the return payload (species season, per-site stated season, month-by-month count, nearest stays by straight line), the filtering rule that out-of-season sites are excluded and counted, and the epistemic caveat 'Never promises a sighting'. The straight-line distance note is a genuinely useful data-quality disclosure.

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?

Three dense sentences, front-loaded with the purpose before the payload and filter behavior. The middle sentence is a long run-on enumerating return fields, but every clause carries information an agent needs.

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 correctly takes on the burden of describing what comes back, and it covers the month-filter edge case. Minor gaps remain: what happens when the species is not found, and how limit interacts with per-site results.

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 real meaning to the month parameter — filtered-out out-of-season sites are still counted — which the schema does not say. Species and atoll semantics are already well covered by the schema, so no further lift was needed.

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?

The description names a concrete task — finding where and in which months a given marine species can be seen in the Maldives — and enumerates the supported animals. No sibling tool overlaps with species seasonality, so the scope alone separates it from list_dive_sites or search_resorts.

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 implied rather than stated: the reader can infer it is for trip-timing questions, and the 'With a month...' sentence explains the effect of one filter. There is no explicit when-to-use/when-not guidance or pointer to an alternative tool (e.g. find_nearby for stays, list_dive_sites for site detail).

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

All Esoru by resortlife.travel 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