Skip to main content
Glama

List stack-worth presets

list_stack_presets
Read-onlyIdempotent

Catalog of the 33 gold, silver and platinum stack-worth presets (id, name, metal, weight, unit, purity and fine troy ounces) used by get_stack_worth. Optional metal filter. Palladium and rhodium are not listed (no measured BPC spot). 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": {
      "metal": "silver"
    },
    "name": "list_stack_presets"
  }
}

Input Schema

NameRequiredDescriptionDefault
metalNoOptional metal filter. Palladium and rhodium are not tracked.

Output Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the description only needs to add context. It does: the exact preset count (33), the metals covered, the fields returned, and the reason palladium/rhodium are absent ('no measured BPC spot'), which is genuine behavioral information not present in 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.

Conciseness3/5

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

The substantive content is front-loaded and compact, but the closing pricing/upsell sentence ('Standard tool free; for a version fine-tuned... email for pricing') contributes nothing to tool selection or invocation and dilutes an otherwise tight definition. The parenthetical field list also partly duplicates the output schema.

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 rich annotations, a fully documented parameter and an output schema covering return values, the description supplies everything an agent needs: scope, count, field set, and the exclusion rationale. Only the missing explicit guidance on when to call this versus get_stack_worth directly keeps it from a 5.

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?

There is a single optional parameter with 100% schema description coverage and an enum, so the schema already fully documents it. The description's 'Optional metal filter' and the palladium/rhodium exclusion restate rather than extend the schema, which fits the baseline 3 for high-coverage schemas.

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 ('Catalog of the 33 gold, silver and platinum stack-worth presets') and explicitly ties it to the sibling that consumes it ('used by get_stack_worth'), so an agent can distinguish it from get_stack_worth and list_products without opening a 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?

The 'used by get_stack_worth' phrase gives clear context for when to reach for this tool (to discover preset ids before a worth calculation), and 'Optional metal filter' signals the narrowing case. It stops short of explicit when-not-to-use or naming alternatives such as product_spec, so it is not a 5.

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