Skip to main content
Glama
deeptrue MCP

deeptrue MCP

Official
by deeptrue-ag

Update survey structure

update_survey_structure
Destructive

Patch an existing survey with a documented partial payload and confirm=true to prevent unsupported schema fields from being added.

Instructions

PATCH an existing survey with a documented survey payload only. Requires confirm=true. Do not invent schema fields.

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_uuid": "<survey_uuid>",
      "patch": "<patch>"
    },
    "name": "update_survey_structure"
  }
}

Input Schema

NameRequiredDescriptionDefault
patchYesPartial SurveySerializer payload only (id, json, name, survey_template_uuid)
confirmNo
survey_uuidYes
organizationNoOrganization domain/slug for this call only. It does not persist. HTTP clients can also send X-DeepTrue-Org. Stdio defaults to DEEPTRUE_ORG.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the danger is known structurally; the description earns credit by adding the confirm=true safety gate and the rule that only documented payload fields may be used. It does not state whether the patch merges or replaces the existing structure, which is the main behavioral ambiguity left for a destructive tool, so it is not 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.

Conciseness5/5

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

Three short sentences, front-loaded with the operation, then the prerequisite, then the constraint. No filler, no restatement of the title, and every sentence carries an actionable rule.

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 nested-object, destructive mutation with no output schema and only 50% schema coverage, the description covers the essentials an agent needs to call it safely: the HTTP verb, the confirmation requirement, and payload restrictions. It omits what a successful response contains and whether the patch merges or overwrites, which are meaningful gaps but not blocking.

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 50%, so the description must compensate and does: it supplies the required confirm=true value for a parameter the schema leaves undocumented, and it constrains patch to the documented SurveySerializer fields. survey_uuid is never described beyond its name, and merge-vs-replace semantics for patch remain unstated, keeping it below 5.

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: PATCH an existing survey. The title adds 'structure' and the description constrains the payload to a documented survey payload, which separates it from read siblings like get_survey. It does not explicitly name or exclude a competing mutation sibling such as update_project, so it stops short of a 5.

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?

Gives one hard prerequisite (confirm=true) and one guardrail (do not invent schema fields), which is real usage guidance. It never says when to choose this over update_project or when a patch is inappropriate, and it offers no exclusion conditions, so guidance is implied by constraint rather than routing.

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