Skip to main content
Glama

edit_survey

Idempotent

Rename a survey (its title in the dashboard and editor). Blocks, questions, Flow, and Deploy settings are edited with edit_block, edit_question, edit_flow, and edit_deploy.

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": {
      "survey_id": "<survey_id>"
    },
    "name": "edit_survey"
  }
}

Input Schema

NameRequiredDescriptionDefault
renameNoRename the survey.
survey_idYesSurvey UUID

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds a useful scope boundary (only the survey title changes) but says nothing about permissions, side effects on published versions, or what the response contains. With annotations present, the bar is lower, so a 3 is appropriate.

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?

Two sentences, front-loaded with the core action and followed by the disambiguation clause. Nothing is redundant and every sentence earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, all parameters are documented in the schema, and annotations carry the mutation semantics. For a narrow single-purpose rename tool, the description leaves nothing an agent needs in order to call it correctly.

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%; survey_id and rename.name (1-200 chars, Unicode allowed) are fully documented in the schema. The description confirms the rename targets the survey title but adds no format, constraint, or usage detail beyond what the schema already provides, so the baseline 3 applies.

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?

The description uses a specific verb+resource ('Rename a survey') and immediately disambiguates scope by saying it changes the title in the dashboard and editor only. This makes it clearly distinguishable from the edit_block, edit_question, edit_flow, and edit_deploy siblings it names.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

It states explicitly what this tool does not cover (blocks, questions, Flow, Deploy settings) and routes the agent to the exact alternative tools for each. The when-to-use and when-not-to-use conditions are both spelled out rather than implied.

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