Skip to main content
Glama
Sign In

SYNTHORA x402 Intelligence Mesh

by com.hergertsynthora
OverviewDiscussionsAdmin

ecb_macro

Read-onlyIdempotent

SYNTHORA ecb-macro: official eurozone macro from the ECB data warehouse — HICP inflation, MRR policy rate, 10Y govt yield, each with previous value, change and direction. For macro/rates agents and prediction markets. Official free source, no key. $0.03 USDC x402 Base. [x402: 0.03 USDC per call on Base]

Input Schema

NameRequiredDescriptionDefault
modeNoCompatibility field constrained to latest by the public schema. The currently routed backend ignores it and requests the last two observations of each fixed series. It provides no selectable date/history mode; latest is not a live-feed or freshness guarantee.
regionNoCompatibility field constrained to U2 by the public schema. The currently routed backend ignores this argument and requests its three fixed Euro-area (U2) ECB series; it cannot select another region.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / mode / description
      Added value: +"Compatibility field constrained to latest by the public schema. The currently routed backend ignores it and requests the last two observations of each fixed series. It provides no selectable date/history mode; latest is not a live-feed or freshness guarantee."
    • addedInput schema / properties / region / description
      Added value: +"Compatibility field constrained to U2 by the public schema. The currently routed backend ignores this argument and requests its three fixed Euro-area (U2) ECB series; it cannot select another region."
  2. Changed5 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / examples
      Previous value: -[
-  {
-    "input": ""
-  }
-]New value: +[
+  {}
+]
    • removedInput schema / properties / input
      Removed value: -{
-  "description": "SYNTHORA ecb-macro: official eurozone macro from the ECB data warehouse — HICP inflation, MRR policy rate, 10Y govt yield, each with previous value, change and direction. For macro/rates agents and pr",
-  "examples": [
-    ""
-  ],
-  "type": "string"
-}
    • addedInput schema / properties / mode
      Added value: +{
+  "const": "latest",
+  "type": "string"
+}
    • addedInput schema / properties / region
      Added value: +{
+  "const": "U2",
+  "type": "string"
+}
  3. Changed3 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "input": ""
+  }
+]
    • changedInput schema / properties / input / description
      Previous value: -"product parameters (JSON or text). Example: {\"input\": \"\"}"New value: +"SYNTHORA ecb-macro: official eurozone macro from the ECB data warehouse — HICP inflation, MRR policy rate, 10Y govt yield, each with previous value, change and direction. For macro/rates agents and pr"
    • addedInput schema / properties / input / examples
      Added value: +[
+  ""
+]
  4. Added
  5. Removed
  6. Added

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnly/openWorld/idempotent/non-destructive, so the description's added value is real: it discloses that the source is official, free, requires no key, and that calls cost $0.03 USDC via x402 on Base. That payment/auth context is not available in the annotations and is exactly the kind of detail an agent needs. It omits freshness/update cadence and rate limits, so it is not 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.

Conciseness3/5

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

It is front-loaded and compact, but the pricing is stated twice ("$0.03 USDC x402 Base" and then "[x402: 0.03 USDC per call on Base]") and the "SYNTHORA ecb-macro:" prefix is branding noise. Roughly a quarter of the text does not earn its place.

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 output schema, the description carries the burden of describing returns and does so adequately (three fixed series, each with prior value/change/direction), and it covers source, auth, and cost. The notable remaining gap is freshness — the schema warns latest is not a live-feed guarantee, but the description implies current data without qualification.

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% and the two parameters are already richly documented in-schema (including the caveat that the backend ignores both mode and region). The description adds nothing about parameters, so the baseline 3 for high-coverage schemas applies.

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?

The description names a specific resource (ECB data warehouse) and enumerates the exact series returned — HICP inflation, MRR policy rate, 10Y govt yield — plus the shape of each reading (previous value, change, direction). That level of specificity implicitly separates it from the forex sibling, but it never explicitly contrasts itself with any of the other 26 tools, so it stops short of a 5.

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?

"For macro/rates agents and prediction markets" gives an implied audience and therefore implied usage context, but there is no when-to-use statement, no exclusion, and no named alternative (e.g., fed_watch for US rates). An agent must infer the routing decision on its own.

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

All SYNTHORA x402 Intelligence Mesh toolsInspect
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