Skip to main content
Glama

Публичная ссылка на ответы

share_answers_link

Создает публичную ссылку на ответы респондентов опроса.

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

Input Schema

NameRequiredDescriptionDefault
typeNoРежим выборки ответов: full=все ответы, in=только из answerIds, not_in=все кроме answerIds, answer=один конкретный ответ. По умолчанию full.
date_toNoКонец периода в формате Y-m-d (например 2024-12-31).
quiz_idYesID опроса.
timezoneNoЧасовой пояс для дат (например Europe/Moscow). По умолчанию — timezone пользователя.
answerIdsNoСписок ID конкретных ответов. Используется при type=in или type=not_in.
date_fromNoНачало периода в формате Y-m-d (например 2024-01-01).
is_deletedNoБрать удалённые ответы вместо активных (по умолчанию false).
is_completeNotrue = только завершённые ответы (по умолчанию true).
is_screenoutNoВключать ответы, дисквалифицированные логикой (по умолчанию false).
media_responsesNoЧто показывать по ссылке у аудио- и видеоответов. Не передан — оба флага выключены: по ссылке видно только, как ответили (записью или текстом).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / media_responses
      Added value: +{
      +  "additionalProperties": false,
      +  "description": "Что показывать по ссылке у аудио- и видеоответов. Не передан — оба флага выключены: по ссылке видно только, как ответили (записью или текстом).",
      +  "properties": {
      +    "include_media": {
      +      "description": "«Записи»: метаданные записи и прослушивание или скачивание по ссылке (по умолчанию false).",
      +      "type": "boolean"
      +    },
      +    "include_transcripts": {
      +      "description": "«Текстовые ответы и расшифровки»: текст вместо записи и расшифровки (по умолчанию false).",
      +      "type": "boolean"
      +    }
      +  },
      +  "type": "object"
      +}
  2. First observed

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true, idempotentHint=false, and destructiveHint=false, so the description is essentially a restatement of the title. It omits behavior the agent would want: whether the link is publicly accessible without authentication, whether repeated calls mint new links, and whether links can be revoked (a job left to set_share_link_active).

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 or repetition. It is efficient, though efficiency here comes at the cost of any supplementary detail.

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

Completeness2/5

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

For a tool with ten parameters, nested objects, and a public-access side effect, the description says nothing about link lifetime, security exposure, or the relationship to link-management siblings. With no output schema, the agent also learns nothing about what the returned link looks like.

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 all ten parameters, including the nested media_responses object and the type enum, are documented in the schema itself. The description adds no filtering semantics or defaults beyond that, so the baseline 3 applies.

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: creates a public link to respondents' answers of a survey. This distinguishes it in substance from share_report_link and share_summary_link, though the description never names those siblings explicitly.

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?

No guidance on when to use this tool versus share_report_link, share_summary_link, or get_media_answer_link, and no prerequisites such as quiz ownership or required permissions. The agent must infer selection from the tool name alone.

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