Jokes By Api Ninjas
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| API_KEY | Yes | API key for authenticating with the Jokes 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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| v1jokesC | API Ninjas Jokes API endpoint. |
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 accessing the Jokes API endpoint, leaving no room for confusion or misselection.
A single tool inherently exhibits perfect naming consistency, as there are no other tools to compare against. The name 'v1jokes' follows a clear pattern that includes versioning and the domain, which is appropriate for its purpose.
A single tool is too few for most practical server purposes, as it limits functionality to a single endpoint. This feels thin and restrictive, especially for a domain like jokes where multiple operations (e.g., fetching by category, rating, or type) might be expected.
The tool surface is severely incomplete for a jokes domain. It only provides access to a single API endpoint without support for common operations like filtering by category, type, or rating, which are typical in joke APIs. This will likely cause agent failures when trying to perform varied tasks.