Skip to main content
Glama

create_survey_from_version

Create a new survey from a saved version snapshot, leaving the original survey untouched. The copy gets fresh ids, its own draft link, and the version's settings.

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": {
      "version_id": "<version_id>"
    },
    "name": "create_survey_from_version"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoName for the new survey (default: the version's survey name plus "(restored)")
team_idNoWorkspace for the new survey (default: the original survey's workspace)
version_idYesVersion to copy (id from read_versions)

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the low-risk framing is partially covered; the description still earns credit by specifying that the source survey is untouched and that the result has fresh ids, its own draft link, and the version's settings. It stops short of noting permission requirements or whether repeated calls produce duplicate surveys (idempotentHint=false is not explained).

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 compact sentences, front-loaded with the action and immediately followed by the non-destructive guarantee. No wasted words; slightly less than perfect only because the second sentence is a feature list rather than further routing guidance.

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 not be described, and the description covers the key behavioral facts an agent needs (non-destructive, new identity, settings inherited). The remaining gap is the relationship to the sibling restore_version and any permission/collision behavior, which matter for a create operation.

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 coverage is 100% and each of the three parameters already carries a description including defaults for name and team_id. The description adds no parameter-level meaning, so the baseline 3 applies.

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 plus the source ('create a new survey from a saved version snapshot') and immediately clarifies the non-destructive scope ('leaving the original survey untouched'). That distinguishes it reasonably from create_survey, but it never mentions restore_version, whose name alone suggests overlapping intent, so the differentiation is not fully explicit.

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: it is clear you use this when you want a copy of a version, but there is no explicit when-to-use/when-not-to-use statement and no routing to create_survey or restore_version. The agent must infer the choice from tool names alone.

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