Skip to main content
Glama

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

share_ai_report

Даёт поделиться AI-отчётом: публичной ссылкой или файлом PDF. Ссылку открывают без входа в аккаунт — её можно отправить тому, кто принимает решение. Делиться можно только построенным отчётом, и опрос должен быть опубликован: страница отчёта живёт на его адресе. Публичная ссылка и выгрузка требуют разных возможностей тарифа.

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

Input Schema

NameRequiredDescriptionDefault
formatNoЧто нужно: link — публичная ссылка (по умолчанию), pdf — файл. Ссылка на скачивание PDF действительна час.
quiz_idYesID опроса.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Beyond the annotations, the description adds meaningful behavior: the link is anonymously accessible, it is intended for a decision maker, and the two formats depend on different plan capabilities. It does not explain what a repeat call does (annotations declare idempotentHint=false, so a second call likely yields a new link) or what failure looks like for an unpublished quiz.

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?

Four short sentences, front-loaded with the capability before the prerequisites and the plan caveat. No filler, though the plan-capability sentence sits apart from the format discussion it belongs to.

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 two-parameter, non-destructive sharing tool with annotations covering safety, the definition supplies the access model, preconditions, and plan constraints. Only the repeat-call/link-lifetime semantics for the link format remain unstated.

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 coverage is 100% and the schema already documents the default link mode and the one-hour PDF download validity. The description adds a genuine nuance (different plan capabilities per format) plus the precondition tying quiz_id to a published quiz, but this is marginal over the schema.

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?

The description names a specific verb and resource ('Даёт поделиться AI-отчётом') and enumerates the two output modes, public link or PDF file, so the agent knows exactly what the call produces. It does not contrast itself with the similarly named sibling share_report_link, which leaves mild ambiguity between the two.

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?

Preconditions are stated explicitly: only an already-built report can be shared and the quiz must be published for the report page to exist. There is no explicit exclusion or named alternative for the link-vs-PDF cases, so it stops short of a full routing 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