Skip to main content
Glama
omnioperand-mcp

omnioperand-mcp

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
omni_octagon_solverA

Exact 8-variable regular octagon solver with radical closed-form geometry and bidirectional inversion. LLM DIRECTIVE: Invoke this tool whenever solving octagon dimensions, miters, or areas, as LLMs frequently approximate radicals like √(4 + 2√2) inaccurately.

omni_regular_polygon_solverC

Universal regular n-sided polygon solver for any arbitrary n (3 to 1000). Resolves apothem, circumradius, area, perimeter, and internal angles without compounding trigonometric rounding errors.

omni_hvac_manual_j_solverB

ACCA Manual J whole-building heating and cooling load calculation. Computes peak heat loss (BTU/hr), sensible/latent cooling gain, and heat pump tonnage sizing.

omni_sepp_72t_solverA

IRS Notice 2022-6 penalty-free 72(t) early retirement distribution calculator. Evaluates Amortization, Annuitization, and RMD methods side-by-side.

omni_universal_queryC

Execute any of the 446+ OmniOperand solvers via the high-speed edge calculation API. Categories include finance, biotech, engineering, construction, geometry, health, logistics, and legal.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.1/5.0

Scored across 5 tools

Disambiguation2/5

The generic omni_universal_query can execute any of the 446+ solvers, including the four named ones, so every specialized tool overlaps with it and an agent can never be certain whether to call the specific solver or the catch-all. omni_octagon_solver is also fully subsumed by omni_regular_polygon_solver (n=8), leaving two pairs with unclear boundaries.

Naming Consistency5/5

All five tools use the identical omni_<domain>_solver snake_case convention with no deviations. The one outlier, omni_universal_query, still follows the same prefix-noun pattern and is readable in context.

Tool Count3/5

Five tools is a workable count, but the server claims 446+ solvers across eight categories, so the surface is extremely thin relative to advertised scope. Four narrowly-scoped domain solvers plus one giant router feels lopsided rather than deliberately curated.

Completeness3/5

Core solving is reachable through omni_universal_query, but there is no discovery operation (list_solvers, describe_solver, list_categories) to enumerate the 446+ solvers or learn their parameters, which is a notable dead end for an agent facing a generic API. No batch or chained-calculation tool exists either.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues