Skip to main content
Glama

Duplicate activity

duplicate_activity
Destructive

Copy an activity and its equipment, pricing, and refuges into a new draft.

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": {
      "activity_id": "<activity_id>"
    },
    "name": "duplicate_activity"
  }
}

Input Schema

NameRequiredDescriptionDefault
activity_idYes
business_idNoThe id of the business to act on, from list_businesses. Optional when this connection covers a single business.

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 is a non-read-only, destructive, closed-world operation, so the safety profile is largely covered. The description does add genuinely new behavioral context by stating the output is a new draft rather than a published activity, but it omits whether the source is modified, what permissions are needed, and whether the copy inherits future changes. Note that destructiveHint=true sits somewhat oddly with a pure copy, and the description does nothing to explain why.

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

Conciseness5/5

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

A single sentence with zero filler, front-loading the verb, resource, and the scope of what gets copied. Nothing could be removed without losing information.

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?

For a two-parameter tool with no output schema, the definition covers the essential mechanics and the resulting state (draft). The one meaningful gap is that an agent cannot tell how to reference the newly created copy afterward, since no return-value behavior is described.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 50%: business_id is documented in the schema and points to list_businesses, while activity_id has no description at all. The description partially compensates by making clear that an existing activity is being copied, implying activity_id is the source, but it does not say whether that activity must be published, owned, or accessible, nor how business_id interacts with the source activity's business.

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 gives a specific verb ("Copy") and resource ("activity") and enumerates what is carried over (equipment, pricing, refuges) plus the destination state (a new draft). This distinguishes it well from create_activity, but it never names the likely alternative create_activity_from_template, so an agent must infer the distinction from names alone.

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 only implied: the tool is for duplicating an existing activity, which suggests it applies when a similar trip must be reused rather than built from scratch. There is no explicit when-to-use/when-not guidance, no prerequisite (e.g. source activity must exist and be readable), and no pointer to create_activity or create_activity_from_template as alternatives.

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