Loading ToolBench
National Bureau of Statistics of Moldova (Statbank) PxWeb MCP server for querying statistical data
Three tools with basic schemas and descriptions, but significant gaps in parameter documentation, output schema specification, and error handling guidance. Tool names lack action verbs (subjects, table_meta, query_table are noun-heavy). Parameter descriptions exist but are sparse and lack constraints. No documented output schemas. Error handling is minimal, raw HTTP errors with truncated text provide no recovery guidance. The 'body' parameter in query_table is documented only as a free-form object with an inline comment, not a proper schema. Overall structure is present but falls short of production quality.
Pull data from a table (POST). body is a PxWeb query object. Keep selected cells under ~10,000.
Navigate the database/subject tree. Root (empty path) lists databases ({dbid}). Drill into a database id to get folders (type "l") and tables (type "t", ".px" suffix).
Table definition (dimensions, valid values). Path must end in the ".px" table id.
Tool names lack action verbs. 'subjects', 'table_meta', 'query_table' are noun-heavy and do not clearly signal intent. Should be 'list_subjects', 'get_table_metadata', 'fetch_table_data' to match LLM expectations.
Output schemas are not documented. LLMs cannot plan downstream calls or extract fields without knowing what each tool returns. Add explicit 'returns' documentation for each tool.
The 'body' parameter in query_table is defined as a free-form object with only an inline comment describing its structure. This violates schema clarity, LLMs cannot validate or reason about nested object shapes without a proper JSON Schema definition.
Error handling provides no recovery guidance. Errors like 'Statbank MD: 404 ...' are raw HTTP status codes with truncated response text. Should categorize errors (retryable, user-fixable, fatal) and suggest next steps.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 44 | 2026-07-28+ | v2 |
Parameter descriptions lack constraints. 'path' parameters accept arbitrary strings with no validation hints. Should specify format (e.g., 'must end in .px for table_meta'), length limits, or character restrictions.