PVPC MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ESIOS_API_KEY | Yes | Your e·sios API key for authentication to access the Esios Red Eléctrica de España API |
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| fetch_pricesA | Fetches the Voluntary Price for the Small Consumer (PVPC) prices for a given date range and geographical area. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only one tool, there is no ambiguity; the tool's purpose is clear and distinct.
A single tool follows the verb_noun pattern, which is consistent and descriptive.
The server has only one tool, which is minimal for a domain that could potentially include more operations (e.g., listing areas or historical data). However, for a focused PVPC price fetcher, it is borderline acceptable.
The tool covers the primary use case of fetching prices for a date range and area. Minor gaps like additional filtering options or bulk data retrieval are not critical, but the surface is quite narrow.