Skip to main content
Glama

Metals Api

by io.github.pipeworx-io

Get Latest

get_latest
Read-onlyIdempotent

Get the latest precious and base metal spot prices (gold, silver, platinum, palladium, copper, etc.). Prices are per troy ounce. Optionally specify base currency and metal symbols.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
baseNoBase currency (default "USD"). E.g., "EUR", "GBP"
_apiKeyYesMetals-API key
symbolsNoComma-separated metal symbols to filter (e.g., "XAU,XAG,XPT"). XAU=gold, XAG=silver, XPT=platinum, XPD=palladium, XCU=copper

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
baseYesBase currency code (e.g., USD, EUR)
dateYesDate of the latest prices in YYYY-MM-DD format
ratesYesMetal spot prices per troy ounce, keyed by symbol (e.g., XAU, XAG)
timestampYesUnix timestamp of when prices were captured

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, covering safety. The description adds that prices are per troy ounce and that base/symbols are optional. This is useful but does not disclose potential rate limits, response format details, or any non-obvious behavior beyond the annotations.

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?

The description is two sentences, front-loaded with the primary purpose, and includes only the essential extra details (per troy ounce, optional parameters). No filler or redundancy; every word adds value.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a simple data retrieval tool with rich annotations, a fully documented input schema, and an output schema. The description sufficiently covers the core behavior, units, and optional parameters. No significant gaps remain, and the description is complete for what the tool does.

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 schema already fully documents 'base', '_apiKey', and 'symbols'. The description's mention of optional base currency and symbols is redundant with the schema. It adds no additional semantics or syntax details beyond what the schema already provides, so the baseline score of 3 applies.

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 description clearly states the tool retrieves 'latest precious and base metal spot prices' with specific metals and a per-ounce unit. The verb 'Get' combined with the resource and scope provides a clear, specific purpose. It also implicitly differentiates from siblings like get_historical by emphasizing 'latest'.

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 description implies usage when current spot prices are needed, and notes optional parameters for base currency and symbols. However, it does not explicitly mention when not to use it or name alternative tools (e.g., get_historical for historical data). Usage is clear but not explicitly differentiated from siblings.

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

All Metals Api toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.8/5.0
Disambiguation2/5

Multiple tools have heavily overlapping purposes: ask_pipeworx, ask_pipeworx_beta, and ask_pipeworx_grounded are variants of the same router, and the six polymarket_* tools cover overlapping arbitrage/edge analysis territory. ai_visibility_check vs scan_competitor_ai_presence and discover_tools vs suggest_questions add further boundary ambiguity. While descriptions try to differentiate, an agent could easily misselect among these clusters.

Naming Consistency3/5

Most names are readable snake_case, but there is no consistent verb_noun pattern: verbs vary (ask, get, list, scan, search, suggest, validate, generate, compare) and several tools are named by product prefix (pipeworx_*, polymarket_*) rather than by action. The pattern is predictable within clusters but inconsistent across the set.

Tool Count2/5

33 tools is heavy for the server's stated name, 'Metals Api', which only has two metals-related tools (get_historical, get_latest). Even as a general data-research server, the surface is bloated with memory utilities, subscription management, feedback, trending, and unrelated AI-visibility scanning. The scope mismatch makes the count feel unjustified.

Completeness3/5

The core metals domain is thin: latest and single-date historical prices exist, but there is no time-series range query, no list of supported metals, and no explicit currency conversion endpoint. The broader data-research/subscription/memory surface is relatively complete, but it is disconnected from the server's apparent purpose, leaving notable gaps for a metals-focused agent.

Resources