Skip to main content
Glama

Значения меток ссылки

get_answer_extra_field_values
Read-onlyIdempotent

Показывает, какие значения встречались у метки ссылки в ответах этого опроса. Метки цепляют к ссылке (utm_source, идентификатор ученика, номер курса) и они приходят вместе с ответом; по ним отбирают ответы в отчёте. Сохраняются все параметры ссылки, кроме служебных, объявлены они или нет. Имена, встречавшиеся в завершённых ответах, — в filters.extra_fields у get_quiz_report (или generate_filtered_report); объявленные переменные ссылки опроса — в get_quiz_variables. quiz://{id}/hidden_options — другое (скрытые опции старого API), меток там нет. Этот инструмент отдаёт значения выбранного имени, с поиском и постранично. Отбор по меткам доступен не на всех тарифах.

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

Input Schema

NameRequiredDescriptionDefault
keyYesИмя метки, например utm_source. Взять из filters.extra_fields у get_quiz_report.
pageNoСтраница, с 1.
searchNoИскать среди значений, частичное совпадение.
quiz_idYesID опроса.
per_pageNoСколько значений на странице, от 1 до 100. По умолчанию 20.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / key / description
      Previous value: -"Имя метки, например utm_source. Взять из quiz://{id}/hidden_options."New value: +"Имя метки, например utm_source. Взять из filters.extra_fields у get_quiz_report."
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds genuinely new behavior: all link parameters are stored except service ones whether declared or not, results are searchable and paginated, and the feature is plan-gated. It stops short of describing the returned value structure, which matters since there is no output schema.

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?

Purpose is front-loaded in sentence one, and each subsequent clause earns its place by disambiguating siblings or stating a precondition. It is dense and the label-definition digression slightly delays the 'when to use' routing, but there is no filler.

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 read-only lookup with five well-documented params and no output schema, the definition covers origin, routing, pagination and plan gating. The only gap is that the shape of the returned values (plain list vs. counts) is left to be inferred from the pagination phrasing.

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%, and the description adds little beyond it — the example key (utm_source) and the pointer to filters.extra_fields are already in the schema text. The partial-match nature of search and the per-page default are likewise schema-level facts, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The first sentence states a specific verb and resource: shows which values occurred for a link label in this quiz's answers. It also defines what a link label is (utm_source, student id, course number) and explicitly distinguishes the tool from quiz://{id}/hidden_options, so an agent can identify it without opening the schema.

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

Usage Guidelines5/5

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

Routing is explicit: names come from filters.extra_fields of get_quiz_report (or generate_filtered_report), declared link variables live in get_quiz_variables, and hidden_options is called out as something different that has no labels. A real precondition is also stated — label filtering is not available on every plan.

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