Skip to main content
Glama

Get roof solar potential (Sonnendach)

get_solar_potential
Read-only

Retrieve federal Sonnendach solar suitability for roofs within 5 m of WGS84 coordinates, including class, irradiation, area, orientation, and slope, nearest first.

Instructions

Return the federal Sonnendach solar-energy suitability of the roof surface(s) within 5 m of the given WGS84 coordinates, nearest first: suitability class, mean irradiation per m² (kWh/m²/yr), total roof-surface irradiation (kWh/yr), roof area, orientation and slope. Orientation follows the Sonnendach convention: 0° = south, −90° = east, +90° = west, ±180° = north.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "lat": "<lat>",
      "lon": "<lon>"
    },
    "name": "get_solar_potential"
  }
}

Input Schema

NameRequiredDescriptionDefault
latYesWGS84 latitude (Switzerland: ~45.8–47.9)
lonYesWGS84 longitude (Switzerland: ~5.9–10.6)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.3

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered; the description adds real value on top by disclosing that only roofs within 5 m qualify, that results are ordered nearest first, and the non-obvious orientation convention (0° = south, ±180° = north). It does not mention coverage limits outside Switzerland or empty-result behavior, keeping it below a 5.

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?

Two sentences, purpose front-loaded, then the precise field list, then the one convention an agent cannot infer. No filler or redundant restatement of the schema.

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?

No output schema exists, and the description fully compensates by enumerating every returned field with units (kWh/m²/yr, kWh/yr). For a two-parameter read-only lookup, nothing needed to call or interpret it is missing.

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% and both parameters carry bounds and Swiss range hints, so the schema does the heavy lifting. The description adds only the phrase 'given WGS84 coordinates', repeating rather than extending what the schema states.

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?

Names a specific verb and resource ('Return the federal Sonnendach solar-energy suitability of the roof surface(s)') and pins the spatial scope to 5 m around WGS84 coordinates. The enumerated return fields (suitability class, irradiation, area, orientation, slope) make it unmistakable versus neighbours like get_building or get_elevation.

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

Usage Guidelines3/5

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

The description gives usable context — the 5 m search radius and 'nearest first' ordering — which tells an agent how results will behave. It stops short of explicit when-to-use/when-not guidance or naming an alternative for cases where a full building record is wanted.

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