Skip to main content
Glama
UliRCS

mastr-mcp-server

by UliRCS

search_grid_connections_public

Search grid connection points and locations by type and filters. Retrieve location data, grid connection points, linked units, DSO info, and network parameters for power or gas connections.

Instructions

Search grid connection points and locations (Netzanschlusspunkte) — no auth required.

Find where units connect to the grid. Returns location data, grid connection points, linked units, DSO info, and network parameters. Supports 4 connection types: power generation/consumption and gas production/consumption. Power types include voltage level, control area, and balancing area. Gas types include gas quality and market area.

For grid connection details of a specific unit, use get_grid_connection (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). Shared filter keys (all 4 types): location_mastr, location_name, nap_mastr, nap_name, dso_mastr, dso_name, unit_mastr, postcode, city, municipality, municipality_key, capacity, planned. Power (Strom) types add: voltage_level, voltage_level_id, control_area, control_area_id, balancing_area, metering_location. power_generation also has: unit_types. Gas types add: gas_quality, gas_quality_id, market_area, market_area_id. planned is a boolean (true/false). Dropdown fields accept both label and numeric ID (e.g. voltage_level='Mittelspannung' or voltage_level_id='352'). Example: {'postcode': '49074', 'voltage_level': 'Mittelspannung'}
page_sizeNoPage size (max 5000).
connection_typeYesType of grid connection. One of: 'power_generation' (Stromerzeugung), 'power_consumption' (Stromverbrauch), 'gas_production' (Gaserzeugung), 'gas_consumption' (Gasverbrauch).
Behavior3/5

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

No annotations provided. Description discloses 'no auth required', return data types, and supported connection types. However, misses details on rate limits, pagination behavior, error handling, or response structure.

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?

Description is well-structured with bolded main point, clear paragraphs for returns and types, and efficient one-sentence alternative guidance. No unnecessary 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?

Given no output schema, description adequately covers return data types and connection types. Could improve by detailing output structure or field examples, but overall sufficient.

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%, baseline 3. Description adds significant value beyond schema by explaining filter operators, shared vs type-specific keys, boolean 'planned', and dropdown field format (label/ID).

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?

Description clearly states it searches grid connection points and locations, using specific verb 'Search' and resource 'grid connection points and locations'. It distinguishes from sibling tool get_grid_connection for specific unit details.

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?

Provides explicit alternative tool (get_grid_connection) for specific unit details. Does not directly compare with sibling search tools like search_power_generation_public, but implies this tool is for connection points across all types.

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