Get Joke
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_jokeB | Return a random programming joke as JSON. |
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 'get_joke' has a clear and distinct purpose, making it impossible for an agent to misselect among non-existent alternatives.
The single tool name 'get_joke' follows a consistent verb_noun pattern (get + joke). Since there is only one tool, there is no inconsistency in naming conventions to evaluate, and it adheres to a predictable style.
A single tool is too few for most server purposes, as it limits functionality and scope. While it might suffice for a minimal joke service, it feels thin and lacks depth, potentially hindering more complex agent interactions or broader use cases.
Inferring the domain as joke retrieval, the tool 'get_joke' provides a basic operation. However, there are notable gaps: no ability to filter jokes by category, search for specific jokes, or manage a joke collection (e.g., create, update, delete), which limits the surface's utility for varied agent needs.