Skip to main content
Glama

Файлы из ответов

get_quiz_report_files
Read-onlyIdempotent

Возвращает файловые ответы (загруженные файлы) для конкретного виджета из отчёта. report_uuid берётся из get_quiz_report; widget_id и widget_hash — из get_quiz_structure.

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>",
      "report_uuid": "<report_uuid>",
      "widget_id": "<widget_id>",
      "widget_hash": "<widget_hash>"
    },
    "name": "get_quiz_report_files"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoКоличество записей (по умолчанию 50).
offsetNoСмещение (по умолчанию 0).
quiz_idYesID опроса.
widget_idYesUUID виджета из get_quiz_structure.
report_uuidYesUUID отчёта из get_quiz_report.
widget_hashYesHash виджета из get_quiz_structure.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds that only file-type answers are returned and that results are scoped to one widget, but says nothing about pagination behavior, empty-result cases, or what the response contains.

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?

Two sentences, front-loaded with the purpose and followed by the ID-provenance guidance. No filler and nothing redundant beyond the minor schema overlap.

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 six-parameter read-only query tool with rich annotations and full schema coverage, the description covers purpose, scoping, and parameter sourcing adequately. Pagination and output shape are left entirely to the schema, which is acceptable given the annotation coverage.

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%, including defaults for limit and offset, so the schema carries the parameter burden. The description's provenance notes duplicate what the schema already states ('UUID виджета из get_quiz_structure'), adding little new meaning. Baseline 3 is appropriate.

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 states a specific verb and resource ('Возвращает файловые ответы (загруженные файлы)') and narrows scope to a single widget within a report. It is clearly distinguishable from general report/answer tools, though it never names a sibling it is explicitly not.

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?

It gives a concrete prerequisite chain: report_uuid from get_quiz_report, widget_id and widget_hash from get_quiz_structure. That is strong routing guidance. It stops short of saying when to avoid this tool or which sibling to use for non-file answers.

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