Skip to main content
Glama
UliRCS

mastr-mcp-server

by UliRCS

search_actors_public

Search energy market participants including DSOs, generators, suppliers, and traders using 23 filter keys for name, function, role, location, and status.

Instructions

Search market actors (Marktakteure) — no auth required.

Find energy market participants: DSOs (Netzbetreiber), generators, suppliers, traders, and more. 23 filter keys for name, function, role, location, status, and DSO flags (large DSO, closed distribution network).

NOTE: MaStR stores '&' as fullwidth U+FF06 in company names. Use 'name%' with a substring without '&' for reliable company name searches.

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, bnetza_number, acer_code, vat_id, register_court, register_number, function, roles, industry_group, postcode, city, street, bundesland, nuts_region, status, registration_date, last_update, activity_start, activity_end, dso_large, dso_closed, sme_flag. Dropdown fields (bundesland, function, status, roles, nuts_region, industry_group) accept label or MaStR ID. Boolean fields (dso_large, dso_closed, sme_flag) accept true/false, ja/nein, 1/0. NOTE: MaStR stores '&' as fullwidth U+FF06 — use 'name%' with a substring without '&' for company name searches. Example: {'function': 'Stromnetzbetreiber', 'dso_large': True}
page_sizeNoPage size (max 5000).
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It states 'no auth required', mentions 23 filter keys, and notes the special handling of '&' characters. However, it does not disclose pagination behavior, rate limits, or error responses, leaving some gaps.

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 and well-structured. It front-loads the purpose, uses bold for emphasis, and employs a clear note format. Every sentence adds necessary information without redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the lack of an output schema, the description does not explain return values. It mentions 23 filter keys but not their full meaning (schema does). Pagination limits are partially covered. For a public search tool, more detail on response structure would improve completeness.

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%, so the schema documents all parameters. The description adds value by explaining the operator suffixes for filters, dropdown field acceptance of labels/IDs, boolean field formats, and a notable tip about searching with '&' in company names. This goes beyond the schema.

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 the tool searches for market actors (Marktakteure) and lists examples like DSOs, generators, suppliers. It distinguishes from sibling tools that search other specific domains (power generation, consumption, gas, etc.).

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 implies usage for finding energy market participants but does not explicitly compare to siblings or provide when-not-to-use scenarios. The context of sibling tool names gives some guidance, but the description itself lacks direct usage 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