Skip to main content
Glama

mcp.xynaptic

by io.xynaptic.mcp
OverviewDiscussionsAdmin

commodity-price

Xynaptic Commodity Price — live commodity prices: Brent, WTI, natural gas, copper, aluminum, gold, coal, wheat and 20+ more, with daily change. GET ?asset=copper (or ?assets=copper,gold). Live futures data. [price: $0.020 per call, x402/USDC]

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsNoquery parameters

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • 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: +{
+  "asset": {
+    "description": "example: \"copper\"",
+    "type": "string"
+  },
+  "change_pct": {
+    "description": "example: 1.18",
+    "type": "number"
+  },
+  "currency": {
+    "description": "example: \"USD\"",
+    "type": "string"
+  },
+  "price": {
+    "description": "example: 6.766",
+    "type": "number"
+  }
+}
    • addedInput schema / required
      Added value: +[]
  2. First observed

TDQS

A4/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 disclosure burden and does partially — it reveals the payment model ($0.020 per call, x402/USDC) and that data is 'live futures data'. It does not mention rate limits, latency, or response shape, leaving some gaps, but the pricing/auth disclosure is genuinely valuable context an agent must have before calling.

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?

Dense and front-loaded: identity, asset coverage, invocation example, data freshness, and price all in a few tight fragments. No filler, though the bracketed pricing note at the end is slightly less prominent than a cost signal arguably deserves.

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?

With no annotations and no output schema, the description must cover more, and it leaves the nested 'params' wrapper and the odd presence of 'price'/'change_pct' (which read as output fields, not query inputs) unclarified. For an agent that must construct the call correctly, this ambiguity is a real gap.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds the plural 'assets=copper,gold' comma-separated syntax that is not present in the schema (which only defines singular 'asset'). It also confirms the query-parameter style, adding marginal value beyond the structured fields.

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?

States a specific resource ('live commodity prices') with an explicit asset enumeration (Brent, WTI, natural gas, copper, gold, coal, wheat) plus '20+ more' and 'daily change', which distinguishes it from sibling price tools like crypto-price and energy-price. An agent can identify the scope without opening the schema.

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 shows how to invoke it ('GET ?asset=copper (or ?assets=copper,gold)'), which is useful call syntax, but gives no when-to-use guidance relative to siblings such as energy-price (which also covers natural gas) or industrial-price. Usage context 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 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