Skip to main content
Glama

Текстовые ответы вопроса

get_quiz_report_inputs
Read-onlyIdempotent

Возвращает текстовые ответы (input-виджеты) для конкретного виджета из отчёта. 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_inputs"
  }
}

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 establish readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds that results are limited to text/input widgets of one widget, which is useful scoping context, but says nothing about pagination behavior or result volume even though limit/offset exist.

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 short sentences, no filler, with the resource description first and the identifier dependency chain second. Every clause carries actionable information.

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 read-only, paginated fetch with a fully described schema and no output schema, the definition covers what is needed to call it correctly, chiefly the dependency on the two upstream tools. Only the return shape and paging expectations are left implicit.

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%, so every parameter is already documented, including the provenance notes for report_uuid, widget_id and widget_hash. The description largely restates that provenance rather than adding new meaning, so the baseline of 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: returns text answers (input widgets) for a specific widget from a report. The widget-level scoping distinguishes it from a bulk answers tool such as get_quiz_answers, though no sibling is named explicitly.

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?

Gives concrete prerequisite guidance by naming where each identifier comes from (report_uuid from get_quiz_report, widget_id and widget_hash from get_quiz_structure). It does not state when to prefer this over alternatives like get_quiz_answers, so it stops short of full routing guidance.

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