Skip to main content
Glama

Tiquiz Quiz Funnel

Get a quiz

get_quiz
Read-onlyIdempotent

Return the full content of one quiz or survey: title, introduction, questions with their answers (and which result or how many points each answer gives), results with their short name, texts and the button the visitor really sees on each result page (none when the result has no link), capture form settings, language and mode (profiles or scoring). Use it before suggesting edits, translating or diagnosing. It contains no lead data. Texts are returned in the quiz language and may contain simple HTML formatting.

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

Input Schema

NameRequiredDescriptionDefault
quiz_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely non-obvious behavior: no lead data is included, texts come back in the quiz language, HTML formatting may be present, and button text is 'none' when a result has no link — all useful for interpreting the payload.

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?

It is one dense paragraph but front-loaded with the core action and the enumerated return contents, then closes with two caveats about lead data and language/HTML. Every clause carries information, though the long comma-separated enumeration is harder to scan than a short bulleted structure would be.

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?

With no output schema, the description carries the full burden of describing return values, and it does so comprehensively, including field families and the edge case of missing result links. Minor gaps remain around behavior for an unknown or malformed quiz_id, but nothing essential for calling the tool successfully is missing.

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?

There is a single required parameter with 0% schema description coverage; the schema only supplies a UUID regex pattern. The description implies a single quiz is addressed and mentions nothing about identifier format or where to obtain the id, so it neither compensates for the coverage gap nor adds meaning beyond the schema's own pattern constraint.

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?

The description opens with a specific verb and resource ('Return the full content of one quiz or survey') and then enumerates exactly what that content comprises: title, introduction, questions with answers and their scoring, results with button text, capture form settings, language and mode. This is far more specific than the title and lets an agent distinguish it from list_quizzes (enumeration) and diagnose_quiz (analysis).

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 explicit situational guidance: 'Use it before suggesting edits, translating or diagnosing,' which places it clearly upstream of mutation and diagnostic siblings. It does not name or exclude an alternative by name nor state a when-not-to-use condition, 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