Skip to main content
Glama

List atolls

list_atolls
Read-onlyIdempotent

The Maldives atolls carrying accommodation, with resort counts and lagoon centroid coordinates. Optionally includes each atoll's resort roster.

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

Input Schema

NameRequiredDescriptionDefault
includeResortsNoAttach the resort list for each atoll.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is fully covered. The description adds value by disclosing what is returned (resort counts and lagoon centroid coordinates) since there is no output schema, but it says nothing about ordering, pagination, or whether atolls without accommodation are excluded.

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?

Two tight sentences with no filler, and the primary payload (atolls with counts and coordinates) is front-loaded ahead of the optional flag. The second sentence largely restates the includeResorts parameter, so it earns slightly less than a full score.

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 a single optional parameter, no output schema and fully covered annotations, the description supplies the missing piece the structured data lacks: what the rows contain. Only the return shape details (ordering, whether zero-resort atolls are filtered) are left unstated, which is minor for a listing tool of this simplicity.

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% and the single boolean parameter is already documented with its default, so the schema does the heavy lifting. The description's 'optionally includes each atoll's resort roster' reinforces the same idea but adds no syntax or format detail 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?

States a specific resource (Maldives atolls) plus the payload it returns (resort counts, lagoon centroid coordinates), which is concrete and verb-like enough for an agent to know this is a geographic enumeration tool. It doesn't name a sibling to differentiate against, but no sibling in the list also enumerates atolls, so confusion risk is low.

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: the 'optionally includes each atoll's resort roster' phrasing hints that the roster is a secondary detail, not a reason to call the tool. There is no explicit when-to-use or when-to-prefer-an-alternative statement (e.g. versus search_resorts or find_nearby for location-driven lookups).

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources