Loading ToolBench

Reading the current corpus…

autoform-mcp MCP server · C · ToolBench

autoform-mcp

MCP server for the Autoform API from Slovensko.Digital. Provides tools for searching Slovak corporate bodies (companies, organizations) by name or registration number (IČO/CIN).

<=2025-11-25STDIO1 tools

62/100

Definition Quality83

Protocol Readiness37

Supportability45

Spec posture

Inferred effective spec <=2025-11-25·current baseline 2026-07-28

Static source inference · medium confidence · detected: Logging

Deprecated protocol patterns detected

Summary

Single tool (query_corporate_bodies) with solid naming, comprehensive parameter descriptions, and well-documented input schema. Tool name starts with action verb 'query' and clearly reflects the operation. Parameter descriptions include format specifications, ranges, and examples. Output schema (SearchResult → list[CorporateBody]) is fully documented with Pydantic models. Descriptions are detailed and actionable. The server includes resources and prompts for API discovery. Main gaps: no error handling guidance in tool description (does not advise LLM what to do on rate limits, auth failure, or no results), no output pagination despite API returning up to 20 results, and descriptions could be more concise (current description is ~500 chars vs 50-200 baseline for optimal LLM consumption). Tool annotations present (readOnlyHint, openWorldHint) align with current spec.

Tools (1)

query_corporate_bodiesread onlyauthsource verified83/100

Search Slovak corporate bodies (companies, organizations). Query format examples: - query="name:Slovenská pošta" finds companies with names starting with "Slovenská pošta" - query="cin:36631124" finds the company with IČO 36631124 - query="cin:366" finds all companies with IČO starting with "366" Returns matching records with identification numbers (IČO, DIČ, IČ DPH), addresses, establishment dates, and links to additional registry data.

Issues (4)

HIGHrecovery-guide ↗

No error handling guidance in tool description. LLM does not know what to do if the query returns 0 results, API returns 401, or rate limits are hit.

query_corporate_bodies

MEDIUMtool-description ↗

Tool description exceeds optimal length (~500 chars). Includes format examples inline rather than relying on parameter descriptions.

query_corporate_bodies

MEDIUMpaginated-result ↗

Output pagination not implemented. Although limit caps at 20, no offset/cursor mechanism or next_token provided for clients to fetch additional results. Per pattern, even small result sets should include pagination when API supports iteration.

query_corporate_bodies

MEDIUMaudit-trail ↗

Token injection via environment variable and HTTP headers works, but no audit logging of tool calls. No trace showing which user/agent called the tool, with what parameters, and what the result was. Per pattern, agent actions must be traceable for compliance.

Recommendations

Add error handling guidance to query_corporate_bodies description: 'If no results are found, try broadening the search (e.g. remove diacritics, search by partial name). If you receive a 401, verify the AUTOFORM_PRIVATE_ACCESS_TOKEN is valid and has not expired.'
Reduce tool description length to 100-150 chars; move format examples and detailed guidance into the parameter descriptions where they already exist.
Add offset/cursor pagination: introduce 'offset' (default 0) and/or 'next_token' parameters, and return 'next_token' in SearchResult if more results are available. Document in description: 'Results are limited to 20. Use next_token to fetch the next batch.'
Instrument tool calls with structured logging: record caller identity, tool name, parameters (sanitized of tokens), timestamp, result count, and latency. Log to stderr or integrate with OpenTelemetry for audit compliance.
Add 'active_only' filter explanation: clarify that setting active_only=true excludes entities with a terminated_on date. Advise LLM: 'If searching for a company that may have been dissolved, try active_only=false.'
Document expected format for cin and name parameters: 'cin must be numeric (can include leading zeros); name is case-insensitive and matches from the start of the company name.'

Spec posture evidence

Inferred effective spec: <=2025-11-25.

Relies on Logging (deprecated) - log to stderr or use OpenTelemetry

Score history

Overall score trend

↑ 13 points across a rubric change (v1 → v2)

62/100

Scored	Grade	Overall	Spec posture	Rubric
2026-09-22	C	62	<=2025-11-25	v2
2026-03-09	F	49	-	v1