Skip to main content
Glama
UliRCS

mastr-mcp-server

by UliRCS

search_power_consumption_public

Find large electricity consumers registered in the German MaStR with filters for location, voltage level, and DSO. No authentication required.

Instructions

Search power consumption units (Stromverbrauch) — no auth required.

Find large electricity consumers registered in MaStR. 29 filter keys covering identification, location, dates, voltage level, and DSO checks.

Use this when searching for electricity consumers (not generators).

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: name, mastr_number, mastr_operator, location_mastr, dso_mastr, operator_name, dso_name, postcode, city, landkreis, street, bundesland, municipality, municipality_key, landmark, parcel, country, longitude, latitude, status, commission_date, current_location_date, shutdown_date, planned_date, registration_date, last_update, large_consumers, voltage_level, dso_check. Dropdown fields (status, bundesland, country, voltage_level, dso_check) accept label or MaStR ID. Example: {'bundesland': 'Bayern', 'voltage_level': 'Hochspannung'}
page_sizeNoPage size (max 5000).
Behavior4/5

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

The description discloses that no authentication is required, that it finds large consumers in MaStR, and lists 29 filter keys across categories. Since no annotations are provided, the description carries full burden and does well, though it could mention return format or data freshness.

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 with three short paragraphs: purpose/auth, details, usage guidance. Information is front-loaded and every sentence earns its place.

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, the description could mention what the response contains. It does state it finds large consumers, but lacks specifics. Otherwise, it covers all input parameters and usage context well.

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. The description adds value by explaining filter operator suffixes, listing all filter keys, and providing an example. This goes beyond the schema descriptions, which are brief.

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 it searches for power consumption units (electricity consumers) and distinguishes from generators. It specifies the resource type and verb, and the context signals include a sibling tool for generation, making the purpose unambiguous.

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?

The description explicitly says 'Use this when searching for electricity consumers (not generators),' providing a clear directive and pointing to the sibling tool for generation. This is excellent guidance.

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