Skip to main content
Glama
Sign In

EclipseMission

by com.eclipsemission
OverviewDiscussionsAdmin

Two to four destinations side by side

compare_destinations
Read-onlyIdempotent

The figures a choice between places turns on, for two to four destinations at once, in the order of the site's ranking whatever the order asked: totality and its times, lodging (eclipse-week mean, per person, Eclipse Premium, reading day), both ends of the cloud range, heat, access, airport, the cost of the observation, and the entry regime of one passport or of each passport we cover. get_destination has the rest.

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": {
      "destinations": "<destinations>"
    },
    "name": "compare_destinations"
  }
}

Input Schema

NameRequiredDescriptionDefault
passportNoISO code of the traveller's passport. Without it, one short line per passport we cover.
destinationsYesTwo to four destination keys, as list_destinations returns them.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover safety and idempotency. The description adds useful behavioral context: results are returned in the site's ranking order regardless of the order requested, and it enumerates the compared fields. It does not describe error behavior, but the added ordering rule is meaningful.

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

Conciseness3/5

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

The purpose is front-loaded, but the core sentence is long, dense, and hard to parse, packing ranking behavior and a long list of return fields into one clause-heavy sentence. It is informative but structurally awkward.

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 does a good job listing the compared dimensions and ordering behavior, and it points to get_destination for remaining information. It is nearly complete for a read-only comparison tool, though the return format could be slightly clearer.

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 100%, so both parameters are already documented. The description reinforces that passport affects whether one passport or all covered passports are reported, but it adds little semantic 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?

The description makes clear this compares two to four destinations at once and lists the metrics returned. It also distinguishes itself from get_destination by saying that tool 'has the rest,' though the phrasing is more roundabout than a direct verb+resource statement.

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

Usage Guidelines4/5

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

It gives a clear context: use this for a side-by-side comparison of two to four destinations, and use get_destination for remaining detail. It stops short of explicit exclusions or a crisp 'use this instead of X when' rule.

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

All EclipseMission 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