Skip to main content
Glama

Get someone’s plan

get_plan
Read-only

The activities one person does on a trip, in order: the shared plan, with their lane’s activities where the group splits. The user’s own plan unless person is given. A surprise kept from the user shows as “Surprise” with only its times: don’t guess at it or try to find out what it is.

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": {
      "tripId": "<tripId>"
    },
    "name": "get_plan"
  }
}

Input Schema

NameRequiredDescriptionDefault
personNoA person’s id, from get_trip’s people
tripIdYesThe trip’s id, from list_trips

Output Schema

NameRequiredDescriptionDefault
activitiesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedOutput schema / properties / activities / items / properties / attachments
      Added value: +{
      +  "description": "Its tickets and files, oldest first, to open in the app; none for a surprise kept from you",
      +  "items": {
      +    "additionalProperties": false,
      +    "properties": {
      +      "name": {
      +        "type": "string"
      +      },
      +      "size": {
      +        "description": "In bytes",
      +        "maximum": 9007199254740991,
      +        "minimum": -9007199254740991,
      +        "type": "integer"
      +      },
      +      "type": {
      +        "description": "Its media type: application/pdf, image/jpeg, image/png or image/webp",
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "name",
      +      "type",
      +      "size"
      +    ],
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
    • addedOutput schema / properties / activities / items / properties / icon
      Added value: +{
      +  "description": "The art someone picked for it, from the app’s library; null while the app picks it by what it is",
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • changedOutput schema / properties / activities / items / required
      Previous value: -[
      -  "id",
      -  "title",
      -  "type",
      -  "date",
      -  "endDate",
      -  "startTime",
      -  "endTime",
      -  "timeZone",
      -  "place",
      -  "endPlace",
      -  "endTimeZone",
      -  "notes",
      -  "laneId",
      -  "surprise"
      -]New value: +[
      +  "id",
      +  "title",
      +  "type",
      +  "date",
      +  "endDate",
      +  "startTime",
      +  "endTime",
      +  "timeZone",
      +  "place",
      +  "endPlace",
      +  "endTimeZone",
      +  "notes",
      +  "laneId",
      +  "surprise",
      +  "icon",
      +  "attachments"
      +]
  2. 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=true, destructiveHint=false, openWorldHint=false, so the safety profile is covered. The description adds real behavioral context the annotations cannot: surprise activities are redacted to 'Surprise' with only times, and the agent is instructed not to probe further — an important privacy/behavioral constraint.

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?

Three sentences, front-loaded with the returned content before the parameter default and the surprise caveat. Nothing is wasted, though the first sentence is dense enough to require a second read.

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?

Output schema exists so return shape needn't be explained, annotations cover safety, and both parameters are documented. The redaction rule is a strong addition; only the relationship to sibling retrieval tools (get_trip) is left unstated.

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 baseline would be 3, but the description adds meaning the schema does not: omitting `person` returns the caller's own plan, and the schema's `person` doc only says where to get the id. That default-resolution semantics is a genuine addition.

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 specifically what is returned: 'The activities one person does on a trip, in order' including the shared-vs-split-lane merging rule. This distinguishes it from siblings like get_trip (trip metadata) and get_lists without the agent needing to open 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 Guidelines3/5

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

Gives a clear default-selection rule ('The user’s own plan unless `person` is given'), which is genuinely useful usage context. However, it never names an alternative tool or an explicit when-not condition, so routing between get_plan and get_trip is left implicit.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources