Skip to main content
Glama

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

share_report_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_report_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
quiz_idYesID опроса.
is_deletedNoБрать удалённые ответы вместо активных (по умолчанию false).
is_completeNoТолько завершённые ответы (по умолчанию 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.6/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false and openWorldHint=true, so the description does not need to re-state that this is a write action with external exposure. What is missing is meaningful context beyond that: that the created link exposes survey data publicly, whether repeated calls mint additional links (idempotentHint=false), and how the filter flags affect what the link reveals. For a privacy-sensitive public-link creation, that is a significant gap.

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 redundancy. Its brevity is clean, though it borders on under-specification rather than tightness.

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?

With five parameters, a nested object, no output schema, and no annotations describing return values, the description should explain what the resulting link is and what the filter flags do to it. It leaves the agent without enough context to invoke the tool confidently for anything but the simplest case.

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%, so every parameter, including the nested media_responses object, is already documented. The description adds no meaning about how is_deleted, is_complete, is_screenout, or media_responses shape the shared report, so baseline 3 applies.

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

Purpose3/5

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

The sentence names a specific verb and resource ("Создает публичную ссылку на отчет опроса"), so the action is identifiable. However, it does not distinguish this from the several sibling share-link tools (share_answers_link, share_summary_link, share_ai_report), leaving the agent to infer what kind of report is being shared and how it differs from those alternatives.

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?

There is no statement of when to use this tool versus the other share_* tools, and no prerequisites or side effects are mentioned. The agent must guess whether the report type or audience determines the choice.

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