Loading ToolBench
Model Context Protocol server for Age of Empires 2 chat assistant
Two tools with basic schemas and descriptions, but significant gaps in parameter documentation and output schema clarity. Tool names lack action verbs (unitStatsLookup, buildOrderSuggestion use camelCase nouns rather than verb_noun pattern). Descriptions are present but generic, unitStatsLookup at ~180 chars is reasonable, but buildOrderSuggestion lacks specificity on what 'follow up' and 'counter' mean. Parameters have types and brief descriptions, but lack constraints (enums, ranges, formats). No documented output schemas visible in source. Error handling and recovery guidance absent. Composition is reasonable (two distinct concerns), but parameter naming could be clearer (mapName, openingName are human-friendly but lack type suffixes).
Recommends a build order for a given civilization, map and/or opening name. Will also provide a follow up build order if requested or a counter build order if requested.
Retrieves comprehensive statistics for specific units including attack values, armor classes, movement speed, range, and special abilities. Optimal for queries about exact unit specifications and capabilities.
Tool names do not follow verb_noun pattern. 'unitStatsLookup' and 'buildOrderSuggestion' are noun-heavy; should be 'get_unit_stats' and 'suggest_build_order' to signal action to LLM.
No output schemas documented. LLMs cannot plan downstream calls or extract fields without knowing response structure. unitStatsLookup should document fields like attack, armor, range, speed; buildOrderSuggestion should document build steps, timings, unit counts.
Parameters lack constraints. 'mapName' and 'openingName' accept free-form strings with no enum or validation. Should declare valid values (e.g., mapName: enum [Arena, Black Forest, Nomad, ...]) to prevent hallucinated inputs.
Inferred effective spec: <=2025-11-25.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 50 | <=2025-11-25 | v2 |
buildOrderSuggestion description is vague. 'Follow up build order' and 'counter build order' are undefined, does follow-up mean next 5 minutes? Next age? Counter to what opponent? Descriptions must answer WHEN and HOW to use the tool.
No error handling or recovery guidance. If mapName is invalid or openingName not found, tool likely returns generic error. Should return 'Map not found. Available maps: Arena, Black Forest, ...' to enable LLM self-correction.