Skip to main content
Glama
Sign In

FareDice

by com.faredice
OverviewDiscussionsAdmin

Change a FareDice trip's nights or places

edit_trip
Read-onlyIdempotent

Change one stop of a FareDice trip and re-chain the rest: night_more or night_less there (the flights after it move a day), night_from_next or night_to_next (a night moved from or to the next stop; the trip's end holds), add_stop (a place after it, with city; without city, the places that fit, each with its change and link) or drop_stop (the stop left out). Returns the new trip as get_trip does, with how much the flights change, how far the end moves and any airport it changes (airports_change). Without change, every change the stop can take, each with its link. 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>",
      "stop": "<stop>"
    },
    "name": "edit_trip"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNoWith add_stop: the place to add (its name or IATA city code), from the list add_stop gives without it.
linkYesA FareDice trip link, as find_trips returns it (https://faredice.com/trip?l=... or /sea/trip?l=...).
stopYesWhich stop to change: 1 is where the first flight lands, 2 the next, and so on.
changeNoThe change to make. Leave it out for the list of changes this stop can take.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Goes well beyond the annotations by disclosing the cascade semantics ("the flights after it move a day", "the trip's end holds"), the return payload (new trip, flight delta, end move, airports_change), and the pricing/quota regime (20 free calls/day per caller UTC, then US$0.01 paid via x402/USDC on Base). The one gap: it never resolves whether the original trip is mutated, which matters because annotations claim readOnlyHint=true while the description says "Change"; "Returns the new trip" hints at a computed result but does not say so outright.

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?

Front-loaded with the core action and free of filler, but the body is a single long run-on with deep nested parentheses, which makes it slower to parse than it needs to be. The pricing/quota sentence is long yet earns its place as decision-relevant cost information.

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

Completeness5/5

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

For a four-parameter mutation-with-recompute tool with no output schema, the description covers the action set, the cascade rules, the fallback no-change discovery mode, the return shape, and non-obvious cost/rate constraints. Nothing an agent needs in order to call it correctly appears to be missing.

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 semantic value the schema lacks: it explains the effect of each enum value (night_more moves the following flights a day, night_from_next keeps the trip's end, add_stop's city dependency) rather than just listing them. `link` and `stop` are already fully documented in the schema, so no credit there.

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?

"Change one stop of a FareDice trip and re-chain the rest" states a specific verb, a bounded resource (one stop), and the recomputation side effect. It enumerates the six change modes so an agent knows exactly what operations are in scope, distinguishing it from sibling read tools like get_trip and find_trips.

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 explicitly states when to omit `change` ("Without change, every change the stop can take, each with its link"), which is a real usage rule an agent would otherwise miss. It also implies the add_stop two-step (call without city to get the list, then with city). It does not route against the closest sibling, swap_stop, which is only mentioned in the pricing sentence, so the alternative-selection guidance is incomplete.

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