Skip to main content
Glama

Переименование опроса

rename_quiz
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>",
      "name": "<name>"
    },
    "name": "rename_quiz"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesНовое название опроса (максимум 80 символов).
quiz_idYesID опроса, который нужно переименовать.

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, idempotentHint=false, and openWorldHint=false, so the safety profile is known. The description adds nothing beyond them: it does not explain that the previous name is overwritten (relevant given destructiveHint=true), whether the return value is empty, or whether renaming affects published links or reports.

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 zero padding. Nothing is wasted, though there is also very little content, so brevity comes at the cost of under-specification rather than being a flaw of wording.

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 mutation with no output schema, the description should at least state what the operation replaces or returns. With only two well-documented parameters and full annotation coverage the call is technically executable, but an agent lacks the context to predict consequences.

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 both quiz_id and name are already documented, including the 80-character limit. The description adds no meaning beyond the schema, which is the expected baseline when the schema does the work.

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 ('Переименовывает существующий опрос') so an agent immediately knows the operation and target entity. It does not differentiate from any sibling or scope the operation further, but the verb 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 guidance on when to use this versus other quiz-modifying tools, no preconditions (does the quiz need to be unarchived?), and no note that the value passes through the same validation as the original name. The agent must infer everything from the name.

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