MCP server with Bearer token OAuth authentication that serves programming jokes
The Joke Server is a minimal, single-tool implementation with severe definition gaps. The tool `tell_joke` has a description but lacks a complete input schema. The server is ostensibly a demonstration of OAuth authentication integration rather than a production-grade tool, and quality baselines are not met. Definition Quality baseline for A+ tools requires 100% of params described, all tools with schemas, and descriptions between 50 - 200 chars optimized for LLM selection; this server provides none of those. The description 'Get a programming joke' is only 24 chars (below the median 194 chars) and provides no context on return format, when to call this tool, or what makes it different from similar humor tools. No input parameters are documented (the schema is empty `{}`), which meets the minimal bar but fails to meet the pattern:tool-description standard of non-empty parameter descriptions for every parameter. The tool itself is trivial (returns a string from a hardcoded list), so output structure is simple but entirely undocumented in the code.
Get a programming joke
Tool description is too short (24 chars; baseline is 194 chars, p10=34, p90=392). Lacks context on return type, use case, and differentiation from similar tools.
No output schema documented. LLMs cannot infer that the tool returns a string or plan downstream operations. Pattern requires documented return types for 100% of A+ tools.
Input schema is empty `{}`. While there are no parameters to document, a clarification that 'this tool takes no input' should be explicit in the description or schema documentation.
Tool name 'tell_joke' is idiomatic but description does not explain when to call this vs. other joke/entertainment tools, or what differentiates this from a general joke API.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-22 | F | 49 | 2026-07-28+ | v2 |
| 2026-03-09 | F | 35 | - | v1 |