Skip to main content
Glama

Переменные опроса

get_quiz_variables
Read-onlyIdempotent

Возвращает скрытые переменные опроса (UTM / extra_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": {
      "quiz_id": "<quiz_id>"
    },
    "name": "get_quiz_variables"
  }
}

Input Schema

NameRequiredDescriptionDefault
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=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered elsewhere. The description contributes only the content hint that the returned variables are the hidden UTM/extra_fields set; it says nothing about output shape, empty-result behaviour, or access restrictions.

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?

One short sentence with the resource and the returned content front-loaded and no filler. It is efficient, though the terseness leaves useful detail unstated rather than because every needed element is present.

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?

This is a simple one-parameter read tool with full annotation coverage, so the description is nearly sufficient. However, with no output schema, the description could have said what the returned variables look like (key/value map, scope, empty case), which is the main remaining gap.

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?

There is a single required parameter, quiz_id, with 100% schema description coverage ('ID опроса'), so the schema already carries the semantics. The description adds no further meaning about the identifier, which matches the baseline-3 case for high schema coverage.

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 ('Возвращает скрытые переменные опроса') and narrows the content with '(UTM / extra_fields)', so an agent knows it is fetching hidden tracking/extra fields for a quiz. It does not explicitly distinguish itself from near-neighbours such as get_quiz_hidden_options or get_quiz_widgets_hidden, 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 Guidelines2/5

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

The description gives no when-to-use or when-not-to-use guidance and names no alternative tool. An agent must infer from the phrase 'hidden variables' alone that this is the tool for UTM/extra_field data rather than the hidden-options or widget variants.

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