Skip to main content
Glama
Sign In
trivia-mcp-server

trivia-mcp-server

by Sankar2316
OverviewSchemaSourceRelated ServersDiscussionsAdmin

get_trivia_questions

Retrieve random trivia quiz questions from Open Trivia Database for interactive applications. Specify question count and difficulty.

Instructions

Get random trivia quiz questions from Open Trivia Database

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": {
      "amount": "<amount>"
    },
    "name": "get_trivia_questions"
  }
}

Input Schema

NameRequiredDescriptionDefault
amountYesNumber of questions (1-20)
difficultyNoDifficulty level

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are provided, so the description bears full burden. It describes a read operation ('Get'), which is non-destructive, but lacks details such as randomness guarantees, duplicate behavior, or data source limitations.

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?

Single sentence, 10 words, front-loaded with purpose, no unnecessary 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 simple tool with two well-described parameters, no output schema, and a clear sibling, the description is sufficient but could mention randomness in more detail.

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?

Input schema has 100% description coverage, so baseline is 3. The description adds context ('random') but does not enhance understanding of individual parameters beyond schema.

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 clearly states the verb 'Get' and resource 'random trivia quiz questions', and differentiates from the sibling tool 'list_trivia_categories' which lists categories, not questions.

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?

The description implies usage for retrieving questions, but does not explicitly state when to use this tool versus the sibling list_trivia_categories or provide any conditions or exclusions.

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

Deploy Server

Other Tools