SooTool
Related Servers
Alternatives to SooTool
No user-submitted related servers found.
Related Servers
- AlicenseBqualityBmaintenanceEnables LLMs to run arbitrary-precision integer and bitwise operations, endianness swaps, IEEE 754 float decomposition, hashing/checksum/modular math, data codecs, statistics, and trigonometry through 29 specialized tools. Its chained batch execution engine lets multiple dependent steps run in one call, eliminating multi-turn round-trip overhead.296 npm17MIT
- AlicenseBqualityBmaintenanceEnables AI agents to perform accurate local computations including arbitrary-precision math, date handling, unit conversion, subnet calculations, encoding, hashing, and text analysis, all without network calls or API keys.270MIT
- AlicenseNot gradedqualityAmaintenanceProvides exact, deterministic tools for math, dates, units, validation, and more to AI agents, returning precise answers with explicit assumptions and warnings instead of model guesses.MIT
- AlicenseAqualityBmaintenanceEnables language models and users to perform exact arithmetic, symbolic math, unit/date conversions, statistics, and read-only SQL queries over registered files, with every operation logged by a citable ID that humans can re-run.11MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to perform exact-decimal double-entry accounting by calling tools that compute money, validate and post entries, verify equations, and produce deterministic audit hashes and citation-grounded artifacts.32 npm1MIT
- FlicenseNot gradedqualityCmaintenanceEnables precise financial analysis of AI agent costs, including token pricing, multi-step run estimates, model comparison, and ROI versus human labor, with deterministic decimal math.-
TDQS
Scored across 286 tools
The 286-tool surface contains many closely related calculators across tax, finance, payroll, and math, so an agent faces frequent misselection risk. Examples include forward_price vs futures_price, tax.kr_income vs tax.progressive vs tax.kr_comprehensive_income_tax, and core.calc vs the dedicated arithmetic tools. Descriptions help within domains, but the overall set has too many overlapping boundaries.
Tool names consistently use a domain-prefixed snake_case convention such as finance.bond_ytm, engineering.beam_deflection, tax.kr_gift, and units.fx_convert. The verb/noun pattern varies between actions and noun phrases, but the namespace and casing pattern are highly predictable throughout the server.
286 tools is far beyond an appropriate scope for a single MCP server, even for a broad multi-domain calculator. The sheer size makes discovery, selection, and maintenance impractical, and strongly suggests the surface should be split into smaller focused servers.
The server covers many domains broadly, including arithmetic, finance, tax, statistics, units, engineering, and policy management, but coverage is uneven. There are notable gaps such as t-distribution density/CDF tools despite t-tests, limited tax jurisdictions, and incomplete lifecycle support in several specialist domains. Agents can complete many tasks but will encounter dead ends.