Skip to main content
Glama

What is my stack worth today

get_stack_worth
Read-onlyIdempotent

Melt value of a gold, silver or platinum stack at Bullion Price Check's hourly spot snapshot (checked hourly, never described as a live price): fine troy ounces, melt, a 95% estimated dealer price, recorded published buyback bids when we have them, and prior-day and prior-week spot change from stored BPC history. Each item is a catalog preset (list_stack_presets) or a custom metal, weight, unit and purity. Optional dealer_premium_pct (0-50) is applied to estimated value. Figures are estimates, not quotes and not financial advice. Palladium and rhodium are not tracked. Standard tool free; for a version fine-tuned or customized to your business, email for pricing via https://bullionpricecheck.com/contact/.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "items": [
        {
          "preset": "1-oz-silver-eagle",
          "quantity": 10
        },
        {
          "unit": "ozt",
          "metal": "gold",
          "weight": 1,
          "purity_pct": 99.99
        }
      ]
    },
    "name": "get_stack_worth"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemsYesStack items (1-100). Each item is a preset id or name, or a custom metal/weight/unit/purity_pct, plus optional quantity.
dealer_premium_pctNoDealer premium in percent applied to estimated value (0-50, default 0 = melt).

Output Schema

NameRequiredDescriptionDefault
okNo
urlNo
toolNo
errorNo
itemsNo
staleNo
termsNo
creditNo
totalsNo
cadenceNo
freshnessNo
spot_asofNo
data_as_ofNo
deprecatedNo
disclaimerNo
disclosureNo
source_urlNo
attributionNo
spot_sourceNo
customizationNo
canonical_toolNo
data_age_minutesNo
deprecation_noteNo
dealer_premium_pctNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior5/5

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

Annotations already establish readOnly/idempotent/closed-world, and the description adds substantial behaviour on top: the price basis is an hourly snapshot explicitly 'never described as a live price,' a 95% estimated dealer price is included, buyback bids appear only 'when we have them,' and prior-day/prior-week change comes from stored history. It also discloses the estimate-not-quote, not-financial-advice framing and that palladium and rhodium are unsupported — exactly the caveats an agent needs before presenting numbers to a user.

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

Conciseness3/5

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

The core purpose is front-loaded in the first clause, and the output/caveat content is packed efficiently. However, the long parenthetical dashes make the opening sentence hard to parse, and the closing sales line about emailing for a custom-priced version is marketing that does not help an agent decide or invoke, diluting the definition.

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 read-only, two-parameter valuation tool this covers what an agent needs: input modes, premium behaviour, price basis, tracked/untracked metals, and the estimate disclaimer. It is slightly more complete than required since a return-value explanation overlaps the existing output schema, but nothing essential is missing.

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%, with per-field docs for preset, metal, weight, unit, purity_pct, quantity and dealer_premium_pct, so the schema already carries parameter meaning. The description adds only light framing — that each item is a preset or a custom metal/weight/unit/purity, and that dealer_premium_pct (0-50) is applied to the estimated value — which is largely a restatement. Baseline 3 is appropriate.

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 opens with a specific verb+resource: computing 'melt value of a gold, silver or platinum stack' against an hourly spot snapshot. It scopes the tool as a stack-level valuation (distinct from single-item melt or preset listing) and names list_stack_presets as the source of item identifiers, so an agent can tell it apart from siblings without opening the schema.

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?

It states the two valid input modes clearly: each item is 'a catalog preset (list_stack_presets) or a custom metal, weight, unit and purity,' and that dealer_premium_pct is optional. It also rules out untracked metals. It stops short of naming when to prefer a sibling such as melt_value or quote for a single item or a firm bid, so it gives context but no explicit alternatives.

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.

Resources