No user-submitted related servers found.
Scored across 2 tools
The two tools have clearly distinct purposes: read_invoice extracts full contents while check_invoice returns only the validation verdict. Their descriptions explicitly cross-reference each other to prevent confusion, so an agent can easily select the right one.
Both tool names follow a consistent verb_noun pattern (read_invoice, check_invoice), using snake_case and clear action words. The only minor deviation is that they are not from the same action family (read vs. check), but this is acceptable given the distinct operations.
With only 2 tools, the surface is quite thin, but for a focused invoice-processing server that offers exactly two complementary operations (read and check), it may be sufficient. However, typical MCP servers have more tools, so this feels slightly minimal.
The domain appears to be electronic invoice handling, and the two tools cover content extraction and validation. Missing operations include invoice creation, listing, or deletion, but for an analysis/validation service, these might be out of scope. Still, there is no way to manage invoices, so the surface is incomplete for a full lifecycle.