Skip to main content
Glama
omnioperand-mcp

omnioperand-mcp

omni_net_metering_credits

Calculate annual solar net metering and feed-in tariff value, self-consumption savings, and export credits from generation and rate inputs.

Instructions

Solar Net Metering & Utility Feed-in Tariff Calculator. Calculate annual financial compensation under NEM 1.0, NEM 2.0, NEM 3.0 (California solar billing), and avoided cost wholesale credit tariffs. Discipline: ENERGY. Governing mathematical model / formula: Net Value = (Self-Consumed kWh × Retail Rate) + (Exported kWh × Feed-in Tariff).

USAGE GUIDELINES:

  • WHEN TO USE: Invoke for deterministic calculation of total_annual_value (Total Annual Solar Value), self_consume_value (Avoided Retail Import Savings), export_credits (Grid Export Credit Earnings), effective_rate_per_kwh (Blended Solar Value ($/kWh)) using annual_gen_kwh (Annual Solar Production (kWh) in kWh), self_consume_pct (On-Site Self-Consumption (%) in %), retail_import_rate (Retail Grid Import Rate ($/kWh)), export_credit_rate (Grid Export Credit Rate ($/kWh)). 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.

DISAMBIGUATION & BOUNDARIES:

  • Use this dedicated specialist tool for 'Solar Net Metering & Utility Feed-in Tariff Calculator' rather than generic dispatchers like omni_universal_query.

  • For multi-calculation chained jobs, use 'omni_batch_calculate'.

  • To inspect schema fields, see 'omni_describe_solver'.

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): "net-metering-credits"

    • category (string): "energy"

    • name (string): "Solar Net Metering & Utility Feed-in Tariff Calculator"

    • formula (string): Governing mathematical formula string

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

    • metrics (object): Dictionary of computed outputs:

      • metrics.total_annual_value (Total Annual Solar Value): Formatted display string (e.g. '$1,870.00')

      • metrics.self_consume_value (Avoided Retail Import Savings): Formatted display string (e.g. '$1,408.00')

      • metrics.export_credits (Grid Export Credit Earnings): Formatted display string (e.g. '$462.00')

      • metrics.effective_rate_per_kwh (Blended Solar Value ($/kWh)): Formatted display string (e.g. '$0.17 / kWh')

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

Input Schema

NameRequiredDescriptionDefault
annual_gen_kwhNoAnnual Solar Production (kWh) (kWh). Estimated annual electricity generated. Default: 11000. Min: 2000. Max: 100000.
self_consume_pctNoOn-Site Self-Consumption (%) (%). % of solar electricity consumed inside the building instantly. Default: 40. Min: 10. Max: 95.
export_credit_rateNoGrid Export Credit Rate ($/kWh). NEM 3.0 export credit or wholesale avoided cost. Default: 0.07. Min: 0.02. Max: 0.6.
retail_import_rateNoRetail Grid Import Rate ($/kWh). Cost paid when buying electricity from grid. Default: 0.32. Min: 0.08. Max: 0.75.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.2

TDQS

A4.9/5.0
Behavior5/5

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

With no annotations supplied, the description carries the full burden and does so: it declares read-only, idempotent, stateless behavior with zero side effects, and explains out-of-bounds input handling that returns a diagnostic error status instead of throwing an exception. It also discloses the response envelope, including status, echoed inputs with applied defaults, metrics, and execution time.

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?

The content is front-loaded with purpose, formula, and usage rules, and uses terse ALL-CAPS section headers that are easy to scan. There is some redundancy, though: the product name is repeated three times, and the units are duplicated (for example, '(kWh) in kWh'), which adds noise without adding meaning.

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, the description supplies the formula, the bounds, the error semantics, a full enumeration of returned fields, and sibling routing. Nothing an agent needs in order to call it correctly or to interpret the result is missing.

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

Parameters5/5

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

Schema coverage is 100%, but the description goes beyond units by spelling out each parameter's role in the formula and naming the output each one drives (for example, self_consume_pct feeds self_consume_value and export_credit_rate feeds export_credits). It also restates default, minimum, and maximum bounds for every parameter, so the baseline of 3 is exceeded.

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 ('Solar Net Metering & Utility Feed-in Tariff Calculator') and gives the governing formula: Net Value = (Self-Consumed kWh × Retail Rate) + (Exported kWh × Feed-in Tariff). This makes it immediately distinguishable from generic math or financial siblings such as omni_net_present_value.

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 section names all four outputs and inputs, and WHEN NOT TO USE excludes qualitative reasoning and non-numeric inputs. It also gives concrete routing rules: use this tool instead of omni_universal_query, use omni_batch_calculate for chained jobs, and use omni_describe_solver for schema inspection.

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