Skip to main content
Glama
Sign In

APIVerve

by com.apiverve
OverviewDiscussionsAdmin

Platinum Price

PlatinumPrice
Read-only

Platinum Price: Platinum Price retrieves real-time spot rates for platinum per troy ounce, gram, and kilogram. Each response reports prices in USD, 24-hour net price changes, direction markers, and update timestamps; paid plans add 172 currencies, 7- and 30-day changes, 30-day stats, and hourly and daily history. (Cost: 2 credits)

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

Input Schema

NameRequiredDescriptionDefault
dailyNoInclude the daily closing price per ounce for the last 30 days
hourlyNoInclude hourly price data for the past 24 hours
currencyNoThe currency to get the price inUSD

Output Schema

NameRequiredDescriptionDefault
dataNo
errorNoError message, null on success
statusNo"ok" on success

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

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, openWorldHint=true, destructiveHint=false, so the safety profile is covered. The description adds genuinely new context: a 2-credit cost per call, plan-gated data tiers, and the fields present in each response. It stops short of rate limits or failure behavior, which keeps it at 4 rather than 5.

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?

Two dense sentences that front-load the core purpose, with cost noted last. The only waste is the redundant 'Platinum Price: Platinum Price' header that merely repeats the name and title.

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?

For a zero-required-parameter read tool with full schema coverage, annotations, and an output schema, the definition covers purpose, response shape, cost, and tier limits. Nothing essential is missing, though the paid-plan gating of the optional booleans could be stated more precisely.

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?

Schema coverage is 100%, so all three parameters are already documented, giving a baseline of 3. The description adds meaning beyond the schema by tying non-USD currencies and hourly/daily history to paid plans, though the phrasing ('paid plans add ... hourly and daily history') leaves it ambiguous whether the daily/hourly booleans are themselves gated.

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 and resource: 'retrieves real-time spot rates for platinum per troy ounce, gram, and kilogram.' The metal is unambiguous, so an agent can distinguish it from GoldPrice, SilverPrice, and PalladiumPrice without opening any schema.

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?

Usage is implied by the resource (fetch platinum spot price), and the mention of paid-plan extras hints at tier limits, but there is no explicit when-to-use/when-not guidance and no routing to alternatives such as CurrencyRate, ExchangeRate, or the other metal-price siblings.

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

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