Skip to main content
Glama

Готовый умный отчёт

get_ai_report
Read-onlyIdempotent

Отдаёт готовый AI-отчёт по опросу — тот самый, что автор видит в разделе результатов. Отчёт состоит из трёх независимых разделов: текстовый анализ, сравнительный и количественный. У каждого свой статус: готов, строится прямо сейчас или не построен, и почему — мало ответов либо нет подходящих вопросов. Читать отчёт этим инструментом, а не запускать генерацию заново: она тратит лимит тарифа.

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

Input Schema

NameRequiredDescriptionDefault
quiz_idYesID опроса.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), yet the description still adds real substance: three independent sections, three possible per-section statuses, and the reasons a section may be absent (too few responses, no matching questions). It does not cover edge cases such as an unknown quiz_id or whether a partially-built report still returns content, so it stops just short of exhaustive.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, front-loaded with what is returned before the status model and the usage warning. Every clause carries information an agent needs — no filler, no repetition of the title.

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

Completeness5/5

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

With no output schema, the description takes on the burden of explaining the return shape and does so: three named sections plus an enumerated status model with failure reasons. Combined with annotations, an agent has enough to call this correctly and interpret the result.

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?

The single quiz_id parameter is fully documented in the schema (100% coverage), so the schema carries the semantics. The description adds no extra meaning about the parameter, which is acceptable at this coverage level but not additive.

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?

Names a specific verb and resource ("Отдаёт готовый AI-отчёт по опросу") and pins the scope precisely — the same report the author sees in the results section. It is clearly distinguishable from generate_ai_report, which the description explicitly contrasts against.

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?

Gives an explicit when/when-not: read with this tool, do not trigger regeneration, and states the cost reason (it burns the plan limit). The alternative behavior is named even though the sibling is only referenced descriptively rather than by exact tool name.

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