sens-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| resolve_operatorA | Resolve a natural-language city or company name to the exact OSD (distribution operator) and default retailer strings the SENS API expects. Example: query="Kraków" or query="enea". Handles typos via fuzzy matching. |
| search_tariffsA | Discover valid tariff codes tailored to a customer profile (household, small business, or industry), optionally narrowed by zone preference and operator. |
| get_pricesA | Fetch composite electricity prices and rate breakdown for a given OSD +
tariff, optionally scoped to a retailer, date, market, region, and annual
consumption. When
|
| get_tariff_componentsC | Inspect the detailed fixed/variable rate components of a tariff, as approved by URE (the Polish energy regulator). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| market_cheat_sheet | Polish electricity market cheat sheet: OSDs, tariff groups, price components. |
TDQS
Scored across 4 tools
Each tool targets a distinct stage in the workflow: resolution of operator names, tariff discovery, tariff component inspection, and price fetching. No overlapping responsibilities or ambiguous boundaries.
All four tools follow a consistent verb_noun pattern with snake_case (resolve_operator, search_tariffs, get_tariff_components, get_prices). The verbs (resolve, search, get) are clear and uniform.
Four tools is well-scoped for a focused API covering Polish energy tariffs and prices. Each tool serves a distinct, necessary function without redundancy or bloat.
The tool set provides a complete workflow: resolve an operator, search for tariffs, inspect tariff components, and fetch prices with breakdowns. No obvious gaps or dead ends exist for the stated purpose of retrieving energy pricing information.