Skip to main content
Glama
omnioperand-mcp

omnioperand-mcp

omni_list_solvers

Discover deterministic calculators across disciplines, filter by category, and search by keyword to find the exact solver slug and formula before inspection or execution.

Instructions

Enumerate & Search OmniOperand Solvers: Discovers and lists deterministic calculators across all disciplines with optional category filtering and keyword search matching solver names, descriptions, and formulas.

USAGE GUIDELINES:

  • WHEN TO USE: Invoke to find the exact calculator slug and governing formula before calling 'omni_describe_solver' or executing via a specialized tool or 'omni_universal_query'. Eliminates blind guessing of slugs.

  • DISAMBIGUATION & BOUNDARIES: Returns summary lists of solvers. To inspect exact input field parameter names, types, and bounds for a discovered slug, call 'omni_describe_solver'.

BEHAVIOR & SAFETY:

  • Pure deterministic query. Read-only, idempotent, and stateless. Zero side effects.

RETURNS:

  • Structured JSON containing:

    • total_matches (number): Count of matching solvers

    • category_filter (string|null): Applied category filter

    • search_query (string|null): Applied search query

    • solvers (array): Array of { slug, name, category, formula_display, fields_count, metrics_count }

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "omni_list_solvers"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of results to return (default 50, max 100).
searchNoOptional keyword search query to match against solver names, descriptions, or mathematical terms (e.g. 'rebar', 'mortgage', 'tonnage', 'voltage drop').
categoryNoOptional discipline category filter (e.g. 'finance', 'engineering', 'construction', 'geometry', 'biotech', 'health').

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.3

TDQS

A4.6/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are supplied, so the description carries the full burden and does: it declares the tool read-only, idempotent, stateless, and side-effect free, and characterizes results as summary lists rather than full solver details. It also discloses the return shape, which no output schema provides.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the purpose, then clearly sectioned into usage, boundaries, safety, and returns. The headers add some length, but in the absence of annotations and an output schema each section carries non-redundant information, so nothing is clearly wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a three-optional-parameter discovery tool with no annotations and no output schema, the description covers trigger conditions, the sibling hand-off, the safety profile, and the exact return fields including per-solver attributes. An agent has everything needed to call it and interpret the response.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so all three parameters are already documented with defaults, bounds, and examples; baseline is 3. The description adds only marginal meaning, noting that search matches names, descriptions, and formulas, but never mentions the 'limit' parameter or its default and cap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: 'Discovers and lists deterministic calculators across all disciplines' with optional category filtering and keyword search. It explicitly contrasts itself with 'omni_describe_solver', so an agent can distinguish the discovery step from the inspection step without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The WHEN TO USE block names the concrete trigger (find the exact slug and formula before calling omni_describe_solver or executing) and explains the value (eliminates blind guessing of slugs). The DISAMBIGUATION section names the alternative and the condition that selects it: use omni_describe_solver for exact input field names, types, and bounds.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools