Riddles By Api Ninjas MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| API_KEY | Yes | API key for authenticating with the Riddles By Api Ninjas API |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| v1riddlesC | API Ninjas Riddles API endpoint. Returns one or more random riddles. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The tool's purpose is clearly defined as fetching random riddles, leaving no room for confusion or misselection.
Since there is only one tool, naming consistency is inherently perfect. The tool name 'v1riddles' follows a single pattern, and there are no other tools to compare it against for inconsistency.
A single tool is too few for a server focused on riddles, as it lacks basic operations like getting riddles by category, difficulty, or ID. This minimal scope limits functionality and makes the server feel incomplete for its apparent domain.
The tool surface is severely incomplete for a riddles domain. It only supports fetching random riddles, missing essential operations such as retrieving specific riddles, filtering by parameters, or managing user interactions. This creates significant gaps that will hinder agent workflows.