Skip to main content
Glama
Sign In

api

by video.quiz
OverviewDiscussionsAdmin

Get quiz play results

quiz_video_get_quiz_results
Read-onlyIdempotent

See how people did on a quiz you own: plays, completions, average score, and the hardest questions. Results are aggregated and hold no personal data. Scores are computed from answers submitted by the browser, so treat them as engagement data, not exam records.

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": {
      "quizId": "<quizId>"
    },
    "name": "quiz_video_get_quiz_results"
  }
}

Input Schema

NameRequiredDescriptionDefault
quizIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare the operation as read-only, idempotent, and non-destructive. The description adds meaningful behavioral context beyond that: results are aggregated, contain no personal data, and are derived from browser-submitted answers, so they should not be treated as authoritative exam records.

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?

The description is three tight sentences, front-loads the returned metrics, and then adds privacy and reliability caveats. Every sentence contributes useful information with no filler.

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 simple read-only analytics tool with annotations covering safety, no output schema, and one required parameter, the description is nearly complete: it lists the returned metrics and explains data provenance and privacy limitations. The main gap is that quizId itself is not described beyond the ownership implication.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema has 0% description coverage for the single quizId parameter, so the description needs to compensate. It only implies that the quiz must be owned by the caller and does not explain how quizId is obtained, what format it uses, or what happens if it refers to an unowned or missing quiz.

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 clearly states that this tool returns analytics for a quiz the caller owns: plays, completions, average score, and hardest questions. This is more specific than the title alone and distinguishes it from quiz-definition tools like get_quiz, though it does not explicitly name sibling alternatives.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It provides an ownership prerequisite ('a quiz you own') and a data-usage caveat ('treat them as engagement data, not exam records'). However, it does not explicitly say when to use this versus get_quiz or list_quizzes, nor does it state any exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All api toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources