Skip to main content
Glama
Sign In

Tripmo

by me.tripmo
OverviewDiscussionsAdmin

Ask to join a trip

join_trip
Idempotent

Ask to join a trip with the join link someone shared (https://…/j/…). The trip's owner decides; until then the trip shows in list_trips as requested and can't be read. While the trip is read-only (its Trip Pass refunded, disputed or being refunded), it's refused (forbidden: "This trip can't change for now, so nobody new can ask to join it."): nobody new can ask to join it until it can change again.

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

Input Schema

NameRequiredDescriptionDefault
linkYesThe join link, or just the code after /j/.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the annotations: it discloses the pending-approval state machine, the side effect visible in list_trips, that the trip cannot be read before approval, and the precise failure mode and error text for read-only trips. This is exactly the behavioral context annotations cannot convey.

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 action and input, then the outcome and failure conditions. The embedded quoted error string is slightly heavy but earns its place by letting the agent interpret a refusal. No redundant restating of the name.

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?

With one required param, full schema coverage, no output schema, and annotations covering safety/idempotency, the description fills the remaining gaps: approval workflow, visibility side effect, and error condition. Nothing needed to call this correctly is 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 schema already defines 'link' and notes the bare code after /j/ is acceptable. The description adds the concrete URL shape (https://…/j/…) which helps the agent recognize a valid input, a modest but real gain over the schema.

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?

States a specific verb ('ask to join') and resource ('a trip') plus the required input (join link). An agent can distinguish this from create_trip, get_trip, and list_trips without opening any schema.

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?

Explains the workflow context clearly: the owner decides, and the trip appears in list_trips as requested and unreadable until then. It also names the explicit when-not case (read-only trip due to refund/dispute) with the exact forbidden message. It does not name an alternative tool for cancelling or checking the request, which keeps it short of a 5.

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