Skip to main content
Glama

Список опросов

get_quiz_list
Read-onlyIdempotent

Возвращает список опросов аккаунта. Без параметров — все живые опросы. Можно искать по названию, смотреть отдельную папку, ограничить список одним форматом и открыть архив: архивные опросы в обычный список не попадают. У каждого опроса виден признак is_archived и формат type: regular — обычный опрос со своей страницей, micro — опрос на сайте, он показывается карточкой внутри чужой страницы, и своей ссылки для респондента у него нет. Поле last_answer_at — когда закончен последний ответ, null — ответов нет.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_quiz_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoИскать по названию, частичное совпадение без учёта регистра.
sortNoПоле сортировки: id (по умолчанию), created_at, updated_at, name или last_answer_at — когда закончен последний ответ. По last_answer_at опросы без ответов всегда в конце.
typeNoПоказать только опросы одного формата: regular — обычные, micro — опросы на сайте. Без параметра приходят оба.
limitNoСколько опросов вернуть, от 1 до 200.
orderNoНаправление: desc (по умолчанию) или asc. С last_answer_at: desc — где ответили последними, asc — где ответов давно не было.
offsetNoСколько опросов пропустить.
archivedNotrue — показать архивные вместо обычных. По умолчанию false.
folder_idNoПоказать только опросы этой папки (folder://list).
workspace_idNoID аккаунта из workspace://list. Без него список собирается по всем аккаунтам, к которым есть доступ, — и своим, и тем, куда вас пригласили.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / order
      Added value: +{
      +  "description": "Направление: desc (по умолчанию) или asc. С last_answer_at: desc — где ответили последними, asc — где ответов давно не было.",
      +  "enum": [
      +    "asc",
      +    "desc"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / sort
      Added value: +{
      +  "description": "Поле сортировки: id (по умолчанию), created_at, updated_at, name или last_answer_at — когда закончен последний ответ. По last_answer_at опросы без ответов всегда в конце.",
      +  "enum": [
      +    "id",
      +    "name",
      +    "created_at",
      +    "updated_at",
      +    "last_answer_at"
      +  ],
      +  "type": "string"
      +}
  2. 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 readOnly, idempotent, non-destructive, closed-world behavior, so safety is covered. The description adds genuinely useful domain context — archived quizzes are hidden by default and the micro format has no respondent-facing link — but says nothing about result size, pagination, or ordering interactions beyond what the schema states.

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?

The default behavior and archive caveat are front-loaded, and each sentence carries substantive meaning. It is somewhat long and partly overlaps with the already-detailed schema, which costs it a point.

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 nine-parameter list tool with no output schema, the description usefully documents the returned fields (is_archived, type, last_answer_at) that the schema cannot cover. Missing are any notes on result volume or pagination expectations when limit/offset are used.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3, and the description still adds value by explaining that micro quizzes are embedded cards with no own link and that archived records only appear when the archive is opened. The remark on last_answer_at being null when there are no answers supplements the schema's sort description.

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 — returns the account's quiz list — and defines the default scope (all live quizzes). It does not explicitly contrast with any sibling, though the get_quiz_* siblings clearly fetch sub-resources rather than lists, so confusion is unlikely.

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?

Gives clear conditions: no parameters returns all live quizzes, archived items are excluded from the normal list and require explicitly opening the archive, and the list can be narrowed by name, folder, or format. It does not name alternative tools, but the when-to-use rules are concrete.

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