Skip to main content
Glama

AutoTasker Hub — China Social Data API

opentdb_trivia

Open Trivia DB quiz questions with correct + incorrect answers, difficulty and category. $0.01 USDC.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "opentdb_trivia"
  }
}

Input Schema

NameRequiredDescriptionDefault
amountNo
difficultyNoeasy | medium | hard

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does add real behavioral facts: the response includes both correct and incorrect answers, and each call costs $0.01 USDC, which is useful cost information absent from structured fields. It says nothing about the number of questions returned, payment/auth mechanics, or rate limits, leaving meaningful gaps for a paid tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, front-loaded with the resource and payload, so there is no bloat. However, the 'category' mention is not just wasted space but actively misleading, since no such input exists.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a paid tool with no annotations and no output schema, the description should explain the shape and volume of results and the payment model. It conveys the answer format and price but omits question count semantics, category absence, and any response structure, leaving real ambiguity about what a call yields.

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?

Schema coverage is only 50%, so the description needed to compensate. It mentions difficulty, which matches one parameter, but never explains the 'amount' parameter — an agent cannot learn from the description that amount is the count of questions, defaults to 5, and caps at 20. It also implies a category filter that the schema does not have.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description identifies the resource (Open Trivia DB quiz questions) and the payload (correct + incorrect answers), so an agent can tell roughly what it returns. But it is a noun phrase with no verb, and it lists 'category' as a dimension even though no category parameter exists, which blurs what the tool actually does.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no exclusions, and no reference to any sibling tool. An agent knows this fetches trivia but has no stated condition that selects it over alternatives such as cat_fact or bored_activity.

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.