Your Next Tours

Duplicate Tour Template

duplicate_template

Copy your own template (or a company template open to you) into a NEW template; sub-resources are deep-copied. Params: id (uuid) + body { visibility? }. The copy gets an AUTOMATIC name -- to rename it, call update_template afterwards. The plan quota applies.

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": {
      "id": "<id>",
      "body": "<body>"
    },
    "name": "duplicate_template"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes
`body`	Yes

Output Schema

Name	Required	Description
`id`	No
`city`	No
`name`	No
`tags`	No
`region`	No
`status`	No
`country`	No
`guideId`	No
`category`	No
`language`	No
`tourType`	No
`createdAt`	No	ISO 8601 timestamp
`isCurated`	No
`updatedAt`	No	ISO 8601 timestamp
`tourFormat`	No
`visibility`	No
`description`	No
`publishedAt`	No	ISO 8601 timestamp
`adoptionCount`	No
`broadcastMode`	No
`collectibleId`	No
`coverImageUrl`	No
`organizationId`	No
`routerProfileId`	No
`sourceTemplateId`	No
`estimatedDuration`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 3, 2026

changedOutput schema / properties / adoptionCount / type

Previous value: -[
-  "number",
-  "string"
-]New value: +[
+  "number",
+  "string",
+  "null"
+]

First observedOct 2, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Adds real behavior beyond the annotations: sub-resources are deep-copied, the copy receives an automatic name, and the plan quota applies. Annotations only flag it as a non-idempotent, non-destructive write, so this extra context is valuable; it stops short of explaining what visibility does or what happens when the quota is hit.

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?

Three dense sentences, front-loaded with the core action and scope, then the naming behavior and quota caveat. No filler.

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 the description covers ownership, deep-copy behavior, naming, and quota. The only gap is the meaning of the visibility enum, which affects the resulting template's state.

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?

With 0% schema description coverage the description must carry parameter meaning, and it names both params (id uuid, body with optional visibility) and marks visibility as optional. However it never explains what 'personal' vs 'org' visibility does, so semantics remain thin.

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 and resource ('Copy your own template ... into a NEW template'), and the parenthetical ownership scope plus the sibling names (update_template, duplicate_program) make clear what is being duplicated and what is not.

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?

Gives a clear precondition (your own template or a company template open to you) and routes the agent to update_template for renaming after the copy. No explicit when-not-to-use guidance, but the ownership constraint covers the main eligibility question.

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

All Your Next Tours tools Inspect

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

Need Help?