Skip to main content
Glama
Sign In

Tripmo

by me.tripmo
OverviewDiscussionsAdmin

See what changed

history
Read-only

Changes to a trip, newest first: who made each one (and through which AI, or a friend writing in a pad), when, the reason they gave, and every operation's before and after; undone_by marks one that was undone. Filter by since/until (ISO times), by ("me", a person id or a member id) and record (changes that touched or mention an id). Paged: pass next_cursor as cursor.

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": {
      "trip": "<trip>"
    },
    "name": "history"
  }
}

Input Schema

NameRequiredDescriptionDefault
byNoWhose changes: "me", a person id, or a member id (mem_…).
tripYesThe trip id, e.g. "trp_8Kd2…", from list_trips.
limitNo
sinceNoChanges at or after this time.
untilNoChanges before this time.
cursorNo
recordNoOnly changes that touched or mention this record: any record's id (an item, a member, a note, a finding…).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint/destructiveHint=false, and the description adds genuinely new behavior: newest-first ordering, per-entry contents, undone_by marking reversed operations, and cursor-based paging via next_cursor. It does not mention the default/max page size or rate limits, but the value beyond annotations is substantial.

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?

One dense paragraph, front-loaded with the resource and ordering, then filters, then paging. Every clause carries information, though the parenthetical "(and through which AI, or a friend writing in a pad)" is colorful rather than operational.

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 7 params, no output schema, and a read-only annotation, the description still conveys entry shape, ordering, undo marking, and pagination — enough to call and interpret results. The unmentioned limit parameter and unspecified default page size are the only real gaps.

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 71%, and the description compensates for the biggest gap by explaining that cursor takes next_cursor from a prior page, which the schema leaves bare. It also glosses the meaning of record ('touched or mention') more loosely than the schema, though it omits any mention of limit.

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?

"Changes to a trip, newest first" names the exact resource (a trip's audit history) and the ordering, then enumerates the content of each entry (who, when, reason, before/after). An agent can immediately tell this apart from siblings like write, undo, or query.

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

Usage Guidelines3/5

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

Usage is implied through the filter vocabulary (by/since/until/record), which suggests retrospective investigation. However, no sibling is named and there is no explicit "use this when… instead of X" guidance, so the agent must infer that this is the audit-log tool.

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