SShortSingh.
TopTechnologyAI & MLStartupsProgrammingScienceBusinessFinanceCrypto & Web3World
Back to feed
Programming

Why a VAT Validation MCP Server Uses Two Separate Tools Instead of One

0
·60 views

Developer building vatnode-mcp, the official MCP server for VAT-validation SaaS vatnode, chose to split VAT validation into two distinct tools: check_vat_format and validate_vat_number. The first performs an instant, free, offline regex check to confirm whether a VAT number matches the expected pattern for a given country. The second makes a live network call to the EU's VIES registry to verify whether the number is actually registered and retrieve the associated company name. Combining both into one tool would force every caller to bear the latency and failure risks of a VIES lookup even when only a quick format check is needed. The design reflects a broader API principle: tools with opposite cost and reliability profiles serve different use cases and should remain separate to avoid silently degrading the quality of answers.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Log in to join the discussion and vote.

Log in

Related stories

0
ProgrammingDEV Community ·

Why Multi-Agent Coding Systems Fail in Production and a Proposed Isolation Fix

A technical report argues that many enterprise multi-agent coding projects stall because the same model both writes and judges its own code, letting blind spots compound. The author describes a containment design that partitions state by role, so an orchestrator, a contracts owner, and separate backend and frontend workers each control only their own files. Each phase must pass two independent checks: a clean-room tester that runs real builds and audits, and a read-only auditor that cannot edit what it reviews. After three failed reviews, automated retries stop and the issue is escalated with evidence. The report frames reliability as a state-isolation and control problem rather than a prompting one.

0 comments Read more at DEV Community
0
ProgrammingDEV Community ·

Keep Unowned Stale Vendor TXT Records Until Dependencies Are Confirmed During Mail Cutovers

The piece argues that during an edtech company's mail provider change, unknown vendor TXT verification records should be kept rather than deleted. Its reasoning is that an unowned record may still support a third-party verification dependency, and deleting it is the main risk even though retained records mostly add clutter. It recommends recording ownership when records are created, reviewing the zone periodically, and using stable record names so verifications do not accumulate. The author proposes a review process that keeps approved mail intent separate from the observed DNS state and labels unresolved tokens as needing ownership review. The hypothetical example is framed as illustrative planning rather than measured data.

0 comments Read more at DEV Community
0
ProgrammingDEV Community ·

Seven Java library changes that compile and pass tests but break existing users

A DEV Community article lists seven library changes in Java that compile and pass the library's own tests yet still break its users. The author distinguishes source compatibility, whether callers' code still compiles, from binary compatibility, whether previously compiled code still runs against the new jar. Because applications often update a library without recompiling its dependents, binary compatibility is especially important. Each example is checked on Java 25 and shows the real error messages that result. The article suggests safer alternatives, such as adding overloads, keeping return types, or giving new interface methods default implementations.

0 comments Read more at DEV Community
0
ProgrammingDEV Community ·

KryonOS v3.0.0 Released With New Hardware, Bluetooth, GPS and On-Device AI Support

The developers of KryonOS have announced the official release of version 3.0.0, a major update to the operating system. The release adds support for the LilyGO T-Deck Plus device, including its trackball, keyboard, display, and speaker. It also introduces on-device AI image generation using a 4-million-parameter DCGAN-96 model on supported ESP32-S3 hardware, along with Bluetooth features such as BLE scanning and HID keyboard functionality. Further additions include GPS integration, native MP3 and WAV audio support, image rendering for PNG, JPEG and BMP formats, and encrypted MicroSD backup and recovery. Expanded JavaScript APIs (Level 3) and security and performance improvements are also included, with full release notes available on GitHub.

0 comments Read more at DEV Community