Skip to main content
Glama
rfdez

PVPC MCP Server

by rfdez

Fetch PVPC Prices

fetch_prices

Fetch Spanish PVPC electricity prices for a specified date range and geographical area, with configurable time and geographical aggregation.

Instructions

Fetches the Voluntary Price for the Small Consumer (PVPC) prices for a given date range and geographical area.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
localeNoGet translations for sources. Accepted values: `es`, `en`. Defaults to `es`.es
startDateNoBeginning of the date range to filter indicator values in iso8601 format. E.g. 2025-06-29T00:00:00.000+02:00. Defaults to the start of today.2026-04-29T00:00:00.000Z
endDateNoEnd of the date range to filter indicator values in iso8601 format. E.g. 2025-06-29T23:59:59.999+02:00. Defaults to the end of today.2026-04-29T23:59:59.999Z
timeAggregationNoHow to aggregate indicator values when grouping them by time. Accepted values: `sum`, `average`. Defaults to `sum`.sum
timeTruncationNoTells how to truncate data time series. Accepted values: `hour`, `day`, `month`, `year`.
geographicalAggregationNoHow to aggregate indicator values when grouping them by geographical ID. Accepted values: `sum`, `average`. Defaults to `sum`.sum
geographicalIdsNoTells the geographical IDs to filter indicator values. Accepted values: `3` (España), `8741` (Península), `8742` (Canarias), `8743` (Baleares), `8744` (Ceuta), `8745` (Melilla). Defaults to `8741`, `8742`, `8743`, `8744`, `8745`.
geographicalTruncationNoTells how to group data at geographical level when the geographical aggregation is informed. Accepted values: `country`, `electric_system`.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
pricesYes
Behavior2/5

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

No annotations provided and description does not disclose behavioral traits like read-only, rate limits, or side effects. Relies entirely on schema.

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?

Single sentence with no superfluous information, directly to the point.

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?

Description is minimal given the 8 parameters and no siblings. Output schema exists, so return details are covered, but more context on usage patterns would help.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the description adds no extra meaning beyond the already detailed parameter descriptions. Baseline 3 is appropriate.

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 fetches PVPC prices for a date range and geographical area, using specific verb and resource.

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?

No guidance on when to use, but with no sibling tools, the context is implied. No when-not-to-use or alternatives mentioned.

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/rfdez/pvpc-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server