Skip to main content
Glama

Структура опроса

get_quiz_structure
Read-onlyIdempotent

Возвращает структуру опроса: ids (порядок виджетов), entities (конфиги виджетов), hidden options. Используйте перед update_quiz_widgets и update_quiz_logic.

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_structure"
  }
}

Input Schema

NameRequiredDescriptionDefault
quiz_idYesID опроса.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/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 safety and repeatability are covered. The description adds the shape of what comes back (ids order, entities configs, hidden options), which is useful, but says nothing about size, pagination, or authorization scope beyond the annotations.

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?

Two short sentences with zero waste: the return contents are front-loaded, then the workflow guidance. Nothing could be removed without losing information.

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 single-parameter read with no output schema, the description compensates by listing the returned sections and the workflow position. It is slightly incomplete on return format details (e.g., whether hidden options come only when present), but otherwise sufficient to call the tool correctly.

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?

Only one parameter exists and the schema documents it at 100% coverage ("ID опроса"), so the schema carries the semantics. The description adds no format, source, or lookup guidance for quiz_id, making the baseline 3 appropriate.

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 enumerates the returned components: ids with widget order, entities with widget configs, and hidden options. That is concrete enough to distinguish it from most get_quiz_* readers, though it does not explicitly contrast with the nearby get_quiz_widgets_hidden / get_quiz_hidden_options siblings.

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

Usage Guidelines4/5

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

Explicitly names the two follow-up tools it precedes (update_quiz_widgets, update_quiz_logic), which tells the agent exactly when in a workflow to call it. There are no exclusion conditions (e.g., when a simpler getter suffices), so it stops short of a full when/when-not statement.

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