Skip to main content
Glama
UliRCS

mastr-mcp-server

by UliRCS

search_power_generation_public

Search for wind turbines, solar panels, biomass plants, and other power generation units in the German MaStR register. Filter by energy carrier, location, capacity, status, and more to find specific units.

Instructions

Search power generation units (Stromerzeugung) — no auth required.

The primary tool for finding wind turbines, solar panels, biomass plants, hydro, storage, gas turbines, nuclear plants, etc. in the MaStR register. Supports all 20 energy carriers with 27 filter keys and 10 operators.

Use this as the default search tool for power generation questions. For full unit details after finding a MaStR number, use get_unit (SOAP).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNo1-based page number.
filtersYesFilter dict with optional operator suffixes on each key. Operators: '=' (eq, default), '!=' (neq), '%' (contains), '!%' (not contains), ':' (starts with), '$' (ends with), '>' (gt), '<' (lt), '?' (is null), '!' or '!?' (is not null). Supported filter keys: tech, name, eeg_key, mastr_number, mastr_operator, capacity, capacity_netto, postcode, city, landkreis, street, bundesland, longitude, latitude, status, commission_date, eeg_commission_date, operator_name, wind_park, wind_manufacturer, hub_height, rotor_diameter, solar_park, storage_capacity, storage_mastr_number, storage_technology, battery_technology. tech shortcuts: 'wind', 'solar'/'pv', 'biomass', 'hydro', 'storage', 'geo', 'natural_gas', 'nuclear', 'hydrogen', etc. German aliases also work (erdgas, kernkraft, wasserstoff, etc.). Dropdown fields (bundesland, status, wind_manufacturer, storage_technology, battery_technology) accept label or MaStR ID. Example: {'tech': 'wind', 'bundesland': 'Niedersachsen', 'capacity>': 3000, 'eeg_key!?': ''}
page_sizeNoPage size (max 5000).
Behavior3/5

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

The description states 'no auth required' and implies a read-only search, but with no annotations, the burden is on the description. It does not explicitly declare read-only, rate limits, or other behavioral traits beyond auth. Adequate but could be more transparent.

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?

The description is concise (around 100 words), well-structured with bullet points, and front-loads the purpose. Every sentence adds value, 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?

For a complex search tool with many filter keys and operators, the description covers the essentials: filter syntax, supported keys, tech shortcuts, and dropdown fields. No output schema is provided, but the tool is a search that likely returns a list of units; the description is adequate.

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

Parameters4/5

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

Schema coverage is 100%, but the description adds significant value: it explains filter operators, provides examples, lists tech shortcuts, and mentions German aliases and dropdown field behavior. This goes beyond the schema descriptions.

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?

The description clearly states 'Search power generation units' and lists specific energy carriers (wind, solar, biomass, etc.), distinguishing it from sibling search tools (e.g., search_actors_public). The verb 'search' and resource 'power generation units' are explicit.

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?

The description advises 'Use this as the default search tool for power generation questions' and directs users to get_unit for full details after finding a MaStR number. It provides clear context but does not explicitly exclude other search tools for power generation.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/UliRCS/mastr-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server