Loading ToolBench
MCP server for Thai plate prophecy advice based on date of birth, day of week, and license plate numbers
Thai Plate Prophecy MCP has basic tool definitions with visible schemas and descriptions, but falls short of production quality. All 4 tools have descriptions (10-50 chars, below the 50-200 char baseline for LLM optimization) and parameter schemas with types. However, descriptions are generic and lack context for when/why to use each tool. Parameter descriptions are minimal ('date number of birth date' is redundant). No output schema documentation. Error handling is present but not recovery-focused. Tool naming follows verb_noun convention but lacks clarity on domain (Thai numerology/astrology context is implicit, not explicit). No tool annotations (readOnlyHint, etc.). Overall, this is a functional but under-documented server typical of community projects.
Get advice for all days of the week
Get advice by day of the week
Get advice by date of birth
Get advice by plate number
Descriptions are too short (10-50 chars) and lack context. 'Get advice by date of birth' does not explain WHEN to use this tool, WHAT it returns, or WHY it matters. LLMs need 50-200 char descriptions with use-case guidance.
Parameter descriptions are redundant or uninformative. 'date number of birth date' repeats the parameter name without explaining format, constraints, or valid range. Should be: 'Day of birth (1-31, numeric string)'.
No output schema documented. Handler returns formatted text via mcp.NewToolResultText(), but LLMs cannot see the structure (lucky number, avoid number, avoid character fields). Document return schema in tool descriptions or via structured output.
Inferred effective spec: <=2025-11-25.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 49 | <=2025-11-25 | v2 |
advice_by_day_of_week requires day name as string ('Sunday', 'Monday', etc.) but parameter description does not list valid values. Should declare as enum or provide explicit list: 'One of: Sunday, Monday, Tuesday, Wednesday, Thursday, Friday, Saturday'.
advice_by_dmy accepts date/month/year as separate strings but does not validate format or range. LLMs may pass '32' for day or '13' for month. Add constraints: 'day: 1-31, month: 1-12, year: 4-digit numeric string'.