Loading ToolBench

Reading the current corpus…

jithox-mcp MCP server · B · ToolBench

jithox-mcp

MCP server providing tools for IBAN verification, VAT validation, Peppol e-invoice readiness checking, and Peppol participant lookup

2026-07-28+STREAMABLE_HTTP4 tools

71/100

Definition Quality70

Protocol Readiness72

SupportabilityNot measured-

Spec posture

Inferred effective spec 2026-07-28+·current baseline 2026-07-28

Static source inference · medium confidence · evidence: Streamable HTTP

Current-spec patterns detected

Summary

Jithox MCP provides 4 tools with clear, domain-specific names (verify_iban, check_vat_list_format, check_peppol_ready, lookup_peppol_participant). All tools have descriptions (34 - 194 chars, within baseline range). Input schemas are present with typed parameters and descriptions. However, output schemas are NOT documented in the source, responses are returned as JSON strings that must be parsed by the client, not as structured tool output. Error handling is minimal; no recovery guidance or actionable error messages visible. Tool descriptions lack dependency hints and prerequisites. No tool annotations (readOnlyHint, etc.) despite all being read-only operations.

Tools (4)

check_peppol_readyread onlysource verified65/100

Check if an invoice will be accepted by Peppol before sending it

check_vat_list_formatread only50/100

Free, offline format check for a list of EU VAT numbers. A well-formed number is NOT a registered one.

lookup_peppol_participantread onlysource verified70/100

Look up whether a participant can receive a Peppol e-invoice

verify_ibanread onlysource verified73/100

Verify IBAN format and validity

Issues (5)

HIGHtool ↗

Output schemas not documented. Tools return JSON strings that clients must parse manually (e.g., json.loads(result['content'][0]['text'])). LLMs cannot infer response structure, forcing unstructured parsing and increasing hallucination risk.

verify_ibancheck_vat_list_formatcheck_peppol_readylookup_peppol_participant

MEDIUMtool-annotations ↗

No tool annotations despite all tools being read-only. Missing readOnlyHint declarations prevent agents from understanding safety properties and optimizing caching/retry strategies.

verify_ibancheck_vat_list_formatcheck_peppol_readylookup_peppol_participant

HIGHrecovery-guide ↗

Error handling lacks recovery guidance. No visible error classification (retryable vs. user-fixable vs. fatal) or actionable error messages. Agents cannot self-correct on invalid input.

verify_ibancheck_vat_list_formatcheck_peppol_readylookup_peppol_participant

Recommendations

Document output schemas for all tools. Define the structure of response objects (e.g., verify_iban returns {status, doesNotProve, ...}). Include field types and descriptions so LLMs can extract data reliably.
Add tool annotations: set readOnlyHint=true for all four tools. This signals to agents that these are safe, cacheable, and idempotent operations.
Enhance error messages with recovery guidance. E.g., 'Invalid IBAN format: must be 15 - 34 alphanumeric characters. Example: BE68539007547034' instead of a bare error code.
Add parameter format constraints to descriptions. For check_peppol_ready, specify: invoiceNumber (alphanumeric, max 20 chars), issueDate (ISO 8601), currency (ISO 4217 code), endpointScheme (0208 for VAT ID, etc.).
Document dependencies and prerequisites. E.g., 'lookup_peppol_participant requires a valid Peppol participant identifier (format: scheme::identifier). Use check_peppol_ready first to validate invoice structure.'

Score history

Overall score trend

First recorded score · v2 rubric

71/100

Scored	Grade	Overall	Spec posture	Rubric
2026-09-23	B	71	2026-07-28+	v2