Skip to main content
Glama
omnioperand-mcp

omnioperand-mcp

omni_solar_sizing

Calculates solar array size, panel count, annual kWh output, and roof area from monthly usage, sun hours, panel wattage, and offset target for accurate system planning.

Instructions

Solar Panel Array Sizing & kWh Calculator. Calculate solar panel system size (kW), required roof panels, daily energy generation, and utility offset. Discipline: CONSTRUCTION. Governing mathematical model / formula: System Size (kW) = [Annual kWh / (Sun Hours × 365)] / Derate Factor.

USAGE GUIDELINES:

  • WHEN TO USE: Invoke for deterministic calculation of system_size_kw (Recommended Array Size), panel_count (Total Solar Panels Needed), annual_production (Est. Annual Generation), roof_area_needed (Required Unshaded Roof Area) using monthly_kwh (Monthly Electric Usage in kWh), sun_hours (Average Peak Daily Sun Hours in hrs/day), panel_wattage (Solar Panel Rating in watts), offset_target (Target Electric Bill Offset in %). 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 'Solar Panel Array Sizing & kWh 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): "solar-sizing"

    • category (string): "construction"

    • name (string): "Solar Panel Array Sizing & kWh Calculator"

    • formula (string): Governing mathematical formula string

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

    • metrics (object): Dictionary of computed outputs:

      • metrics.system_size_kw (Recommended Array Size): Formatted display string (e.g. '9.43 kW DC')

      • metrics.panel_count (Total Solar Panels Needed): Formatted display string (e.g. '24 panels (400W)')

      • metrics.annual_production (Est. Annual Generation): Formatted display string (e.g. '13,200 kWh/yr')

      • metrics.roof_area_needed (Required Unshaded Roof Area): Formatted display string (e.g. '432 sq ft')

    • 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_solar_sizing"
  }
}

Input Schema

NameRequiredDescriptionDefault
sun_hoursNoAverage Peak Daily Sun Hours (hrs/day). US average is 4.0 to 5.5 peak sun hours. Default: 4.5. Min: 3. Max: 7.
monthly_kwhNoMonthly Electric Usage (kWh). Average monthly kilowatt-hours from electric bill. Default: 1100. Min: 200. Max: 5000.
offset_targetNoTarget Electric Bill Offset (%). Percentage of electric consumption to offset. Default: 100. Min: 25. Max: 150.
panel_wattageNoSolar Panel Rating (watts). Modern monocrystalline panel: 400W. Default: 400. Min: 300. Max: 500.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.2

TDQS

A4.4/5.0
Behavior5/5

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

No annotations were supplied, yet the description discloses read-only, idempotent, stateless behavior, zero side effects, and that out-of-bounds inputs return a safe diagnostic error rather than throwing. It also explains validation against physical/domain bounds and the return envelope, covering the full burden the missing annotations would otherwise carry.

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?

Purpose and formula are front-loaded, and sections are labeled for fast scanning. The RETURNS block is long and enumerates fields an agent will see anyway at call time, but since no output schema exists that detail is defensible rather than redundant.

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 four-parameter deterministic calculator with no output schema and no annotations, the definition supplies purpose, formula, parameter output mapping, validation behavior, and a full return-shape description. An agent has everything needed to call it correctly and interpret the result.

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%, so units, defaults and min/max for monthly_kwh, sun_hours, panel_wattage and offset_target are already documented in the schema. The description restates those parameters and maps each to an output metric, which is mildly useful but adds no new syntax or constraint detail beyond the schema.

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?

States a specific verb and resource: sizing a solar panel array, computing kW, panel count, annual kWh and offset, plus the governing formula. It clearly distinguishes itself from the generic dispatcher omni_universal_query, though it does not differentiate against the closely named solar-specific siblings present in the catalog.

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?

Gives explicit WHEN TO USE (deterministic sizing computation), WHEN NOT TO USE (qualitative reasoning, non-numeric inputs), and SIBLING ROUTING (prefer this over omni_universal_query, use that for cross-discipline dispatch). Nothing is left to inference.

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