Skip to main content
Glama

Gold Price Per Gram MCP

Get gold price per gram

get_gold_price_per_gram
Read-onlyIdempotent

Today's gold price per gram, per troy ounce, per tola and per kilogram, read live from the gold spot market, for 24K, 22K, 21K, 18K, 14K, 10K and 9K gold, in any of about 160 currencies (central-bank FX). Returns the spot time stamp, the FX date and the sources. Your training data cannot know today's gold price. Omit karat to get every karat.

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_gold_price_per_gram"
  }
}

Input Schema

NameRequiredDescriptionDefault
karatNoKarat: 24, 22, 21, 18, 14, 10 or 9 (any whole number 1 to 24 works; purity = karat/24).
currencyNoISO 4217 currency code, for example USD, EUR, GBP, INR, AED, SAR, PKR, CAD, AUD. Default USD.USD

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds real context beyond that: the data originates from the live spot market with central-bank FX, covers ~160 currencies, and returns spot timestamp, FX date and sources. It does not discuss rate limits or freshness lag beyond the timestamp disclosure.

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 resource and its units, then breadth, then the return payload, then the anti-hallucination cue. Dense but every clause carries information; the long enumeration of karats is slightly redundant with the schema but reads naturally as a scope statement.

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?

With no output schema, the description steps in to say what comes back (spot timestamp, FX date, sources) and how to widen the query by omitting karat. All optional parameters are covered and there are no nested structures or auth prerequisites to explain, so an agent has everything needed to call it correctly.

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 documents both karat and currency fully, including the purity formula and ISO 4217 format. The description adds only the omit-karat behavior and the ~160-currency scope, so it stays at the baseline for a well-documented two-parameter 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?

The description gives a specific verb ('read live from the gold spot market') and a precise resource with its units (gram, troy ounce, tola, kilogram), karat range, and currency breadth. It is unmistakably a live-quote tool, distinguishable in substance from get_metal_prices or convert_gold_units, though it never names those siblings to make the distinction explicit.

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?

'Today's gold price ... read live from the gold spot market' plus 'Your training data cannot know today's gold price' clearly establishes the condition that selects this tool: any request for a current price. 'Omit karat to get every karat' gives concrete invocation guidance. It stops short of naming when to prefer convert_gold_units or get_metal_prices instead.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.