Skip to main content
Glama
Sign In

OunceScout

by com.ouncescout
OverviewDiscussionsAdmin

Get Live Spot Prices

get_live_spot_prices
Read-only

Get live Gold (XAU), Silver (XAG), Platinum (XPT), and Palladium (XPD) spot prices in USD per troy ounce, plus the real-time Gold-to-Silver Ratio (GSR).

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

readOnlyHint=true already tells the agent this is a safe read, so the description has a lower bar. It adds what the payload contains (four metals plus GSR, quoted in USD/troy ounce), but says nothing about refresh cadence, caching, staleness, or failure modes when a market feed is unavailable.

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?

A single, front-loaded sentence with no filler. Every clause carries information: verb, resource, the four symbols, units, and the extra GSR output.

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 does the job of naming the returned data and units, which is the key thing an agent needs to decide whether the response is usable. It stops short of describing the response shape (field names, timestamps, per-metal structure), a minor gap for a no-parameter read.

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?

The tool takes zero parameters, so the baseline is 4; there is nothing the description could clarify. The mention of USD per troy ounce applies to the returned values, not inputs, so it adds no parameter meaning but costs nothing.

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 ('Get'), a specific resource (live spot prices), enumerates the exact metals (XAU, XAG, XPT, XPD) and the units (USD per troy ounce), plus the derived GSR. No sibling overlaps this domain, so the agent can route to it unambiguously.

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?

The 'live' qualifier implies usage for current rather than historical pricing, but the description never states when to use this versus the sibling catalog/calculation tools, nor any prerequisites or exclusions. Usage is inferable but not spelled out.

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

All OunceScout 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