Skip to main content
Glama

solar-home-incentives

by com.energyaisolution
OverviewDiscussionsAdmin

get_node_score

Instant Energy Node Score (0–100 across 7 axes: efficiency, electrification, renewable generation, storage/resilience, financial optimization, carbon, market readiness) plus the single highest-leverage next action, from whatever property facts you have. More inputs → tighter score. [20 anonymous calls/caller/24h; then 100 free calls/key/30d; active Builder required for sustained informational use]

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
apiKeyNoOptional existing EnergyAI key for hosts that cannot change Authorization headers. Use it to retain account identity for discovery and get_builder_upgrade_link after a trial. Removed before tool execution and persistence. Omit when the Bearer header is attached; never show the key to the user.
evTypeNoe.g. own_ev | plan_ev | no_ev
countryNoISO 3166-1 alpha-2 country code. Omit for US.
roofAgeNoe.g. lt_5 | 5_15 | gt_15 | unknown
zipCodeNoOptional postal code of the property. US: 5-digit ZIP. Other countries: local postal code (pass country too). Omit it to use documented national assumptions.
backupNeedNoe.g. whole_home | essentials | none
heatingFuelNoe.g. natural_gas | oil | propane | electric_resistance | heat_pump | wood | other
serviceTypeNoPrimary interest: solar | battery | ev_charger | efficiency | heat_pump | unsure
propertyTypeNosingle_family | townhouse | condo | mobile_home | multi_family | commercial | farm | other
outageConcernNorare | occasional | frequent | severe
monthlyBillUsdNoAlternative to monthlyBillRange: average monthly bill in USD.
monthlyBillRangeNolt_75 | 75_150 | 150_250 | 250_400 | gt_400 | unknown
electricalPanelSizeNoe.g. lt_100 | 100_200 | gt_200 | unknown

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / apiKey
      Added value: +{
+  "description": "Optional existing EnergyAI key for hosts that cannot change Authorization headers. Use it to retain account identity for discovery and get_builder_upgrade_link after a trial. Removed before tool execution and persistence. Omit when the Bearer header is attached; never show the key to the user.",
+  "type": "string"
+}
  2. Changed2 schema fields changed
    • changedInput schema / properties / zipCode / description
      Previous value: -"Postal code of the property. US: 5-digit ZIP. Other countries: local postal code (pass country too)."New value: +"Optional postal code of the property. US: 5-digit ZIP. Other countries: local postal code (pass country too). Omit it to use documented national assumptions."
    • changedInput schema / required
      Previous value: -[
-  "zipCode"
-]New value: +[]
  3. Changed2 schema fields changed
    • addedInput schema / properties / country
      Added value: +{
+  "description": "ISO 3166-1 alpha-2 country code. Omit for US.",
+  "type": "string"
+}
    • changedInput schema / properties / zipCode / description
      Previous value: -"5-digit US ZIP code of the property."New value: +"Postal code of the property. US: 5-digit ZIP. Other countries: local postal code (pass country too)."
  4. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "heatingFuel": "natural_gas",
+    "monthlyBillRange": "150_250",
+    "propertyType": "single_family",
+    "serviceType": "solar",
+    "zipCode": "59715"
+  }
+]
  5. First observed

TDQS

A4.2/5.0
Behavior4/5

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

No annotations provided, so the description carries the full behavioral burden. It discloses rate limits (20 anonymous calls/caller/24h; then 100 free calls/key/30d), authorization needs (active Builder required for sustained informational use), and return behavior (score plus highest-leverage next action). Missing details on error handling or exactly what 'anonymous' vs 'key' means, but substantial transparency.

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

Conciseness5/5

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

Three compact sentences, front-loaded with the core output, then usage flexibility, then rate/auth constraints. No wasted words.

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 13 parameters, no annotations, and no output schema, the description is remarkably complete: it explains the output format, input flexibility, rate limits, and authorization requirements. It could be improved by clarifying what an 'Energy Node Score' represents conceptually or how it differs from sibling scoring tools.

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 baseline is 3. The description adds the meta-instruction 'More inputs → tighter score' but does not elaborate on individual parameters beyond what the schema already documents thoroughly.

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?

Specific verb+resource: 'Instant Energy Node Score (0–100 across 7 axes...)' clearly states what the tool produces and its structure. Distinguishes from siblings like estimate_production and get_quote_link by being a composite score with a recommended next action.

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

Usage Guidelines4/5

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

'from whatever property facts you have. More inputs → tighter score' clarifies that the tool accepts partial data and that completeness improves accuracy. No explicit when-not or alternative tool named, but the context is clear for a scoring tool.

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

All solar-home-incentives toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources