Skip to main content
Glama
Sign In

FareDice

by com.faredice
OverviewDiscussionsAdmin

Open a FareDice trip from its link

get_trip
Read-onlyIdempotent

The trip a FareDice trip link names, as find_trips returns one: its flights with fares, their ages, times where known and cabin-bag notes, nights in each place and the total, with its home hops when it starts from a home airport. A trip whose fares have gone says so and gives the nearest days the same places all have fares again, or none. 20 calls a day per caller (UTC) of find_trips, get_trip, swap_stop and edit_trip are free; after that each costs US$0.01, paid with x402 (USDC on Base). nonstop_fares and nonstop_from are always free.

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": {
      "link": "<link>"
    },
    "name": "get_trip"
  }
}

Input Schema

NameRequiredDescriptionDefault
linkYesA FareDice trip link, as find_trips returns it (https://faredice.com/trip?l=... or /sea/trip?l=...).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior5/5

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

Beyond the annotations (readOnly/idempotent/non-destructive), the description discloses non-obvious behavior: what happens when fares are stale (nearest days the same places have fares, or none), the inclusion of home hops, and the cost model (20 free calls/day shared across find_trips/get_trip/swap_stop/edit_trip, then US$0.01 via x402). No contradictions with annotations.

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?

Two long run-on sentences: the lead front-loads the return payload rather than the action, and the second mixes stale-fare behavior with a multi-tool pricing schedule. All the content is relevant, but the block is dense and could be split so the purpose and the pricing note sit apart.

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 carries the return-shape burden and does so thoroughly (flights, fares, ages, times, cabin-bag notes, nights, totals, home hops, stale-fare fallback). What is missing is error behavior for a malformed or expired link, and the return container/format itself.

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 'link' parameter already documents its format and provenance. The description only reinforces that the link is 'as find_trips returns one', adding no syntax or edge-case detail the schema lacks. Baseline 3 is appropriate.

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 states precisely what resource is returned (a trip, keyed by a FareDice trip link) and explicitly ties it to find_trips' output shape, so it is distinguishable from siblings. It is phrased as an elliptical noun phrase rather than a verb+resource statement, leaving the 'get' verb to the title, which keeps it just short of a 5.

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?

'as find_trips returns one' tells the agent this is the follow-up call after find_trips, i.e. the link comes from there. It also names the pricing/free siblings, which steers choice between them. It never states a when-not condition or an explicit alternative for retrieving a trip another way, so it stops at 4.

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

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