mcp.xynaptic

energy-demand

Xynaptic Energy Demand FR — live French electricity demand (RTE éCO2mix official): consumption MW, day-ahead forecast, CO2 rate g/kWh, per-fuel generation mix. Quarter-hourly freshness. GET (?date=YYYY-MM-DD, default today). [price: $0.020 per call, x402/USDC]

Input Schema

TableJSON Schema

Name	Required	Description	Default
`params`	No	query parameters

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedOct 2, 2026

removedInput schema / properties / body

Removed value: -{
-  "description": "JSON body for POST endpoints (e.g. insurance, ai-chat, production-risk)",
-  "type": "object"
-}

changedInput schema / properties / params / description

Previous value: -"query parameters, e.g. {city: 'Paris', type: 'Appartement'}"New value: +"query parameters"

addedInput schema / properties / params / properties

Added value: +{
+  "co2_g_kwh": {
+    "description": "example: 47",
+    "type": "number"
+  },
+  "consumption_mw": {
+    "description": "example: 35829",
+    "type": "number"
+  },
+  "date": {
+    "description": "example: \"2026-10-02\"",
+    "type": "string"
+  },
+  "forecast_mw": {
+    "description": "example: 47000",
+    "type": "number"
+  },
+  "nuclear_mw": {
+    "description": "example: 37618",
+    "type": "number"
+  }
+}

addedInput schema / required
```
Added value: +[]
```

AddedOct 2, 2026

TDQS

A3.7/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and does disclose meaningful traits: the official upstream source (RTE éCO2mix), quarter-hourly data freshness, and a per-call price with payment rails (x402/USDC). It omits any auth/account prerequisites and error/failure behavior, which would be useful for a paid endpoint.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single dense line that is front-loaded with what the tool returns, then calling convention, then price. Every clause earns its place, though the packing of source, fields, freshness, method and billing into one sentence is borderline overloaded.

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?

With no annotations and no output schema, the description compensates by enumerating returned measures and stating data source, freshness and cost. It is nearly complete for invocation, missing only auth/error expectations and any hint of scoping versus the neighboring energy tools.

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 description coverage is 100% and the only real parameter is a nested 'params' object, so the schema already carries the documentation. The description adds the date format (YYYY-MM-DD) and that it defaults to today, which is genuinely useful but does not go beyond that.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (retrieve live demand) and resource (French electricity demand from RTE éCO2mix) and enumerates the payload fields (consumption MW, forecast, CO2 g/kWh, generation mix). It does not name or contrast with the obvious sibling energy-grid-status, so an agent must infer the distinction itself.

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?

It gives the calling convention for the date parameter and its default (today), which implies when the tool is relevant, but it never says when to prefer this over energy-grid-status, energy-price, or the other energy-* siblings. Usage is implied rather than stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All mcp.xynaptic tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?