Skip to main content
Glama

Новая переменная опроса

create_quiz_variable

Создает скрытую переменную (extra field) для опроса.

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": "create_quiz_variable"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoОпциональный UUID переменной (если не передан — генерируется автоматически).
nameYesНазвание переменной.
quiz_idYesID опроса.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false, so the mutation and safety profile is covered. The description adds one genuinely useful behavioral fact beyond that: the variable is 'скрытая' (hidden), i.e. not shown to respondents. It says nothing about uniqueness of names, auto-generated IDs beyond the schema note, or what the call returns.

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; the core action and scope come first. It is efficient, but the brevity leaves obvious gaps rather than being tight around a complete statement.

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

Completeness3/5

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

For a simple three-parameter create tool with annotations and a fully documented schema, the description covers the essentials of what is created. It omits any note on duplicate-name behavior, side effects on the quiz, or the return value, which an agent would want before calling a creation endpoint.

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 id, name and quiz_id are each documented in the schema itself, including the auto-generation fallback for id. The description adds no parameter-level meaning beyond that, 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?

The description states a specific verb and resource: 'Создает скрытую переменную (extra field) для опроса', and the parenthetical 'extra field' plus 'скрытую' (hidden) clarify the kind of entity being created. It is clear enough to distinguish from delete_quiz_variable and update_quiz_variable by name, though it never explicitly names those siblings.

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?

There is no guidance on when to create a variable versus using a hidden option or other quiz-scoped entities, and no prerequisites or exclusions are stated. The agent must infer usage entirely from the tool name and required quiz_id.

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