mcp.xynaptic

commodity-price

Xynaptic Commodity Price — live commodity prices: Brent, WTI, natural gas, copper, aluminum, gold, silver, platinum, palladium, lithium, coal, wheat and 20+ more, with daily change. GET ?asset=copper (or ?assets=copper,gold). Live futures data. Usage: Use for live commodity spot prices (Brent, gas, gold, copper). French industrial producer prices are available through the xynaptic-catalog tool. [price: $0.020 per call, x402/USDC]

Input Schema

Name	Required	Description	Default
`params`	Yes	query parameters

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 3, 2026
- addedInput schema / properties / params / required
```
Added value: +[]
```
- changedInput schema / required
```
Previous value: -[]New value: +[
+  "params"
+]
```

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: +{
+  "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: +[]
```

First observedOct 1, 2026

TDQS

A3.7/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full burden. It usefully discloses the costing/payment model ('$0.020 per call, x402/USDC') and that the data is live futures, but omits auth requirements, rate limits, and error behavior expected of a paid live endpoint.

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?

Front-loaded with the resource and asset list, but the prose is comma-heavy and repeats itself ('live commodity prices' then 'Live futures data') while the pricing/payment note trails at the end rather than up front.

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?

There is no output schema and no annotations, so the description should explain more. It covers scope, example calls, and cost, but leaves the return shape ('daily change') and the odd schema params (price/currency/change_pct) unaddressed, leaving the agent to guess at the actual contract.

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%, so the baseline is 3. The description adds the query-string syntax '?asset=copper' and a batched '?assets=copper,gold' form, but the schema only defines a singular 'asset' plus response-like fields (price, currency, change_pct), so the added batch hint is only loosely reconciled with the actual input contract.

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 verb+resource ('live commodity prices') and enumerates the covered assets (Brent, WTI, gas, copper, gold, lithium, wheat, etc.), which clearly separates it from crypto-price, security-price, and property-price. An agent can identify the domain 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides an explicit 'Usage: Use for live commodity spot prices' directive and routes a related case (French industrial producer prices) to the xynaptic-catalog sibling. It lacks explicit exclusions for boundary cases like energy-price, which also covers gas/coal, so routing against that sibling is left to inference.

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

Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?