Skip to main content
Glama
Sign In

Tripmo

by me.tripmo
OverviewDiscussionsAdmin

List my trips

list_trips
Read-only

Who this person is (me) and the trips they're in or have asked to join, with their role, and the trips shared with their email to view (shared_with_me: each one's view_link, for get_trip and query; only to read). A trip its owner offered them to take over has offered_to_you (by whom, until when; get_trip's offer says what taking it over needs). Start here. While they're in no trip yet, new_here is true: tell them they're connected, as next says. billing (absent where Tripmo isn't charging: then a trip just starts): whether they can start a trip now (can_create_trip), their plan (none, yearly: Frequent Flyer, lifetime, comp_lifetime: Lifetime as a gift, partner), their unused Trip Passes (create_trip uses one by itself), where to buy one (buy_pass_url), the prices and plans to show them (pricing_url), and fair use while on a plan.

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_trips"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare this as a safe read-only tool. The description adds useful conditional output context such as billing being absent when Tripmo is not charging and new_here being true while no trip exists, but it does not describe auth needs, rate limits, errors, or broader operational behavior.

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

Conciseness2/5

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

The description is a dense run-on paragraph with nested parentheticals and semicolon-separated clauses. It front-loads the main resource, but for a zero-parameter bootstrap/list tool it is overstuffed and hard to parse.

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 burden of explaining return content. It covers identity, current and joined trips, shared trips, offers, new_here, and billing, though it does not fully specify ordering or every possible field.

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?

The tool has zero parameters, so there is no parameter semantics gap to compensate for. The baseline for a no-parameter tool is 4.

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 identifies the core resource clearly: the current person plus the trips they are in, have asked to join, have shared, or have been offered. It distinguishes the shared-trip portion from get_trip and query, though the opening is phrased as returned data rather than a clean action verb.

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?

'Start here' gives an explicit entry-point cue, and the description routes shared trip views to get_trip/query. It lacks an explicit when-not-to-use statement, but the intended first-call role is clear.

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

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