Skip to main content
Glama

Move an activity

move_activity

Moves an activity to another day (null: unscheduled), and into a lane or back to the shared plan. It goes last on that day unless index says where among the day’s activities (0 is first).

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>",
      "activityId": "<activityId>",
      "date": "<date>"
    },
    "name": "move_activity"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYes
indexNo
laneIdNoA lane from get_trip’s splits, or null for the shared plan; left out, it stays
tripIdYesThe trip’s id, from list_trips
activityIdYes

Output Schema

NameRequiredDescriptionDefault
activityYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / properties / laneId / description
      Previous value: -"A lane, or null for the shared plan; left out, it stays"New value: +"A lane from get_trip’s splits, or null for the shared plan; left out, it stays"
    • addedOutput schema / properties / activity / 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 / activity / 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 / activity / 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

A3.8/5.0
Behavior4/5

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

Annotations already declare this is a non-read-only, non-destructive, closed-world mutation, so the safety profile is covered. The description adds genuinely new behavioral rules beyond that: default placement is last on the day, `index` overrides it with 0 meaning first, and omitting laneId preserves the current lane. It does not cover failure behavior (e.g., nonexistent activity or idempotency), which keeps it short of a 5.

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?

Two sentences, front-loaded with the primary action and the destination variants, with the ordering rule as the follow-on detail. The parenthetical '(null: unscheduled)' and nested clauses make it dense but no sentence is wasted.

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?

An output schema exists, so return values need no explanation, and annotations carry the mutation safety profile. For a 5-parameter reordering tool the description covers lane, date, and index interactions adequately; only error/edge behavior and the relationship to sibling mutation tools remains unspecified.

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 only 40%, so the description must compensate, and it does for the weakest-documented parameter: `index` (0 is first, otherwise appended last) and the null/omitted distinction for `laneId` and `date`. That meaning is absent from the schema for `index` and `activityId`, and only the laneId/tripId descriptions partially overlap what the prose says.

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?

States a specific verb and resource ('Moves an activity') plus the dimensions of the move: day, lane/shared plan, and ordering. An agent can tell this is a repositioning operation rather than a content edit, though it never names update_activity as the contrasting sibling for field changes.

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 conditional semantics (null date = unschedule, null laneId = shared plan, omitted laneId = stays put), which tells the agent how to invoke it in different situations. However, there is no explicit statement of when to choose this over update_activity or how it differs from add_activity/remove_activity.

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