Skip to main content
Glama
omnioperand-mcp

omnioperand-mcp

omni_matrix_multiplication

Calculate 2×2 matrix determinant, trace, inverse, characteristic polynomial, and eigenvalues from four entries, eliminating manual arithmetic errors with deterministic results.

Instructions

2×2 Matrix Determinant & Inverse Calculator. Calculate 2×2 matrix determinant det(A), matrix trace, matrix inverse A⁻¹, characteristic polynomial, and eigenvalues. Discipline: CALCULUS. Governing mathematical model / formula: det(A) = ad - bc | A⁻¹ = [1 / det(A)] · [ [d, -b], [-c, a] ].

USAGE GUIDELINES:

  • WHEN TO USE: Invoke for deterministic calculation of matrix_det (Determinant det(A)), matrix_trace (Matrix Trace tr(A)), inverse_row1 (Inverse Row 1 [d/det, -b/det]), inverse_row2 (Inverse Row 2 [-c/det, a/det]) using elem_a (Element a (Row 1, Col 1)), elem_b (Element b (Row 1, Col 2)), elem_c (Element c (Row 2, Col 1)), elem_d (Element d (Row 2, Col 2)). Guarantees exact machine floating-point precision, eliminating LLM arithmetic mistakes and formula hallucinations.

  • WHEN NOT TO USE: Do not use for qualitative evaluations or unquantified reasoning. All input parameters must be valid numerical values.

  • SIBLING ROUTING: Use this dedicated specialist tool for '2×2 Matrix Determinant & Inverse Calculator' rather than generic dispatchers like omni_universal_query. For cross-discipline dynamic dispatch, see omni_universal_query.

BEHAVIOR & SAFETY:

  • Pure deterministic computation with machine floating-point precision.

  • Read-only, idempotent, and stateless. Zero side effects or persistent state mutations.

  • Input validation: All arguments are validated against physical and domain bounds. Out-of-bounds inputs return a safe diagnostic error status without throwing runtime exceptions.

RETURNS:

  • Structured JSON object containing:

    • status (string): "success" on valid execution or "error" if validation fails

    • calculator (string): "matrix-multiplication"

    • category (string): "calculus"

    • name (string): "2×2 Matrix Determinant & Inverse Calculator"

    • formula (string): Governing mathematical formula string

    • inputs (object): Echoed input parameter dictionary with applied defaults

    • metrics (object): Dictionary of computed outputs:

      • metrics.matrix_det (Determinant det(A)): Formatted display string (e.g. '10.0000 (Invertible)')

      • metrics.matrix_trace (Matrix Trace tr(A)): Formatted display string (e.g. '10.0000')

      • metrics.inverse_row1 (Inverse Row 1 [d/det, -b/det]): Formatted display string (e.g. '[0.6000, -0.7000]')

      • metrics.inverse_row2 (Inverse Row 2 [-c/det, a/det]): Formatted display string (e.g. '[-0.2000, 0.4000]')

    • execution_time_ms (number): Latency in milliseconds.

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_matrix_multiplication"
  }
}

Input Schema

NameRequiredDescriptionDefault
elem_aNoElement a (Row 1, Col 1). Top-left entry. Default: 4. Min: -1000. Max: 1000.
elem_bNoElement b (Row 1, Col 2). Top-right entry. Default: 7. Min: -1000. Max: 1000.
elem_cNoElement c (Row 2, Col 1). Bottom-left entry. Default: 2. Min: -1000. Max: 1000.
elem_dNoElement d (Row 2, Col 2). Bottom-right entry. Default: 6. Min: -1000. Max: 1000.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.2

TDQS

A4/5.0
Behavior4/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 it does disclose that the tool is read-only, idempotent, stateless, validated against bounds, and returns a diagnostic error status instead of throwing. The main gap is the unstated singular-matrix case: det(A)=0 makes the inverse undefined, and the description only hints at it via the '(Invertible)' example format rather than saying what is returned.

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

Conciseness3/5

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

The purpose and formulas are front-loaded and headers aid scanning, but the text is padded with template-style section labels and repeated claims ('machine floating-point precision' appears twice, omni_universal_query is referenced in two separate places). Given there is no output schema, the RETURNS block earns its length, but the marketing phrasing around it does not.

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

Completeness4/5

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

With no annotations and no output schema, the description supplies both the safety profile and a full return-shape breakdown including example values, which is what an agent needs to call and interpret this tool. Completeness is only dented by the unfulfilled promise of characteristic polynomial/eigenvalue outputs and the missing singular-matrix behavior.

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 description coverage is 100% — each of elem_a through elem_d already documents position, default, and min/max. The description restates the same names and roles without adding format guidance or constraints beyond the schema, so baseline 3 applies.

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

Purpose4/5

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

The description names a specific resource and operation ('2×2 Matrix Determinant & Inverse Calculator') and gives the governing formulas, so the agent can tell exactly what computation is performed. Two issues keep it from a 5: the tool name 'omni_matrix_multiplication' implies a different operation than determinant/inverse, and the description claims it computes 'characteristic polynomial, and eigenvalues' while the RETURNS section lists only det, trace, and the two inverse rows.

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?

Explicit WHEN TO USE with named output quantities, explicit WHEN NOT TO USE ('qualitative evaluations or unquantified reasoning', all inputs must be numeric), and explicit sibling routing away from omni_universal_query. Nothing is left to inference about when this tool is the right choice.

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