API Ninjas

getGoldSpotPrice

Read-only

Returns the gold spot price (XAU/USD), blended from multiple live market quotes. Free tier returns the last daily close; premium tiers return the live price with bid and ask.

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": "getGoldSpotPrice"
  }
}

Input Schema

Name	Required	Description	Default
`unit`	No	Target unit to convert the price into. Defaults to troy_ounce.	troy_ounce
`currency`	No	ISO 4217 currency code to convert the price into (e.g., EUR, GBP, INR). Defaults to USD.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 9, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Annotations only declare readOnlyHint=true, so the description adds real value: the price is blended from multiple live quotes, free tier returns the prior daily close while premium returns live price, and premium responses include bid/ask. It does not state latency, caching, or update frequency, but the tier-dependent behavior is genuinely useful disclosure.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

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

Two sentences, front-loaded with the resource and quote basis, then the tier caveat. No filler, no redundant restatement of the tool name.

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 for the key case (price, bid/ask, daily close vs live). It omits what a free-tier response actually contains besides a close value, but an agent has enough to call and interpret the tool.

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 'unit' and 'currency' are already documented, including the enum and defaults. The description says nothing about how conversion interacts with the quote (e.g., whether the blend happens before or after FX conversion), adding no meaning beyond the schema.

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?

States a specific resource and quote convention (gold spot price, XAU/USD) plus how it is sourced ('blended from multiple live market quotes'). It never distinguishes itself from the very close siblings getCurrentGoldPrice, getCurrentMetalsPrice, or getCommoditySpotPrice, so an agent must guess which gold/price tool to pick.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance and no named alternative, despite several overlapping siblings (getCurrentGoldPrice, getHistoricalGoldPrice, getCurrentMetalsPrice). The free-vs-premium tier note describes result quality, not when to select this tool.

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

All API Ninjas 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?