SiteCheck Trade & Energy

Live spot price of gold or silver in USD per troy ounce

energy_precious_metals_spot_fix

Read-only

Live spot price of gold (XAU) or silver (XAG) in USD per troy ounce from gold-api.com (aggregated free spot feed, no key). This is a spot quote with a timestamp, not the LBMA London AM/PM fixing and not vault holdings; the route name is kept for the owner. Related tools on this server, for a different need: energy_ammonia_fertilizer_spot when you need monthly US producer price indexes for ammonia and nitrogen; energy_cme_agri_spot_futures when you need monthly world reference prices for corn, wheat and soybeans. Price: $0.002 in USDC per successful call, paid with x402 (Base, Solana or Arc); failed calls are not charged.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "energy_precious_metals_spot_fix"
  }
}

Input Schema

Name	Required	Description	Default
`metal`	No	XAU (gold) or XAG (silver); default XAU

Output Schema

Name	Required	Description	Default
`name`	No
`unit`	No
`metal`	No
`source`	No
`priceUsd`	No
`checkedAt`	No
`quoteUpdatedAt`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered; the description adds real value beyond that by disclosing the upstream source, that no API key is required, that the response is a timestamped quote rather than a fixing, and the paid-call model with the exact price and the note that failed calls are not charged. The main thing missing is any hint about freshness or update cadence of the live feed.

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?

Front-loaded with the core purpose and output units, then exclusions, then routing, then pricing, which is a sensible order. The aside 'the route name is kept for the owner' is internal meta-commentary that does not help an agent decide or invoke anything.

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 one optional parameter, full schema coverage, an output schema covering return values, and annotations covering safety, the description closes the remaining gaps: source, units, what the quote is not, and the payment mechanics. Only a hint on data latency or refresh frequency would make it fully self-sufficient.

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 single enum-less parameter already documents XAU/XAG and its XAU default. The description repeats the two tickers but adds no extra meaning, such as case sensitivity or what happens with an unrecognized ticker, so the schema does the heavy lifting.

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?

The first sentence states a specific verb and resource: live spot price of gold (XAU) or silver (XAG) in USD per troy ounce, with the source named. It then explicitly distinguishes the output from the LBMA London AM/PM fixing and from vault holdings, so an agent can tell what this quote is and is not 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?

It gives clear usage context (a free aggregated spot feed, no key needed) and names two sibling tools with the exact conditions that select them (monthly US ammonia PPI, monthly agri reference prices). The remaining gap is that other closely related metals tools on this server, such as energy_lme_metal_cash_settled, are never mentioned, so the agent gets no guidance on the metals-adjacent choice.

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

All SiteCheck Trade & Energy 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?