Skip to main content
Glama

Правка переменной опроса

update_quiz_variable
Destructive

Обновляет имя скрытой переменной опроса.

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": {
      "quiz_id": "<quiz_id>",
      "field_id": "<field_id>",
      "name": "<name>"
    },
    "name": "update_quiz_variable"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesНовое имя переменной.
quiz_idYesID опроса.
field_idYesUUID скрытой переменной. Взять из quiz://{id}/variables.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=true and idempotentHint=false, so the safety profile is covered. The description adds only that the name field is the sole target; it says nothing about the consequences of renaming a variable (e.g. broken references in existing quiz logic), required permissions, or reversibility – notable gaps for a destructive mutation.

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?

A single front-loaded sentence with no filler. It is efficient, though its brevity leaves the definition under-specified rather than optimally informative.

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

Completeness2/5

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

For a destructive, non-idempotent mutation with no output schema, the description should explain the effect of renaming a hidden variable and any downstream risk. Instead it stops at restating the operation, so an agent lacks the context needed to call it safely.

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 100%, so all three parameters are already documented in the schema, including where to obtain field_id (quiz://{id}/variables). The description adds no new meaning beyond the schema, 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?

The description names a specific verb and resource ('Обновляет имя скрытой переменной опроса') and usefully narrows scope to the name field only, which distinguishes it from the create/delete siblings. It does not explicitly differentiate from update_quiz_logic or other update_* siblings, but the object (hidden variable) is unambiguous.

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

Usage Guidelines2/5

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

No when-to-use guidance, no prerequisites, and no mention of the alternative tools (delete_quiz_variable, create_quiz_variable, update_quiz_logic) are given. The reader must infer the context entirely from the name and schema.

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