Xynaptic Energy Interconnections FR — live French cross-border power exchanges (RTE éCO2mix official): flows MW with England, Italy, Germany-Belgium, Switzerland, Spain (positive = import). GET (?date=YYYY-MM-DD, default today). [price: $0.020 per call, x402/USDC]
| Name | Required | Description | Default |
|---|---|---|---|
| params | No | query parameters |
Changes observed during successful MCP inspections.
Input schema / properties / bodyRemoved value: -{
- "description": "JSON body for POST endpoints (e.g. insurance, ai-chat, production-risk)",
- "type": "object"
-}Input schema / properties / params / descriptionPrevious value: -"query parameters, e.g. {city: 'Paris', type: 'Appartement'}"New value: +"query parameters"Input schema / properties / params / propertiesAdded value: +{
+ "borders": {
+ "description": "example: 6",
+ "type": "number"
+ },
+ "date": {
+ "description": "example: \"2026-10-02\"",
+ "type": "string"
+ },
+ "net_import_mw": {
+ "description": "example: -10246",
+ "type": "number"
+ }
+}Input schema / requiredAdded value: +[]Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations at all, the description carries the full burden and does well: it discloses the paid cost ($0.020/call, x402/USDC), the data source (RTE éCO2mix official), the return unit (MW), and the sign semantics (positive = import). It omits auth mechanics and error behavior, which keeps it short of a 5.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single dense line, front-loaded with resource, source and scope, then the call syntax and price. No filler; every clause carries information an agent needs.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
No output schema and no annotations, so the description must stand alone; it covers the data domain, unit, sign convention, date default and cost, which is nearly everything needed to call it. It does not describe the exact response shape or field list, leaving a small gap.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is nominally 100% but the per-field descriptions are bare examples (e.g. "2026-10-02"), so the prose earns credit by clarifying the date format YYYY-MM-DD, the today default, and the positive-means-import meaning of net_import_mw. The 'borders' field is not explained in prose, keeping it below 5.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb and resource — live French cross-border power exchanges — and names the official source (RTE éCO2mix). It enumerates the borders covered and the sign convention, which cleanly separates it from siblings like energy-grid-status or energy-demand.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies context (live cross-border flows, date defaults to today) but never states when to use this instead of the many energy-* siblings (energy-brief, energy-price, energy-grid-status). Usage is inferable from the resource but no alternatives or exclusions are given.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.