Skip to main content
Glama

StackerScan

Observed premiums over spot

get_observed_premiums
Read-only

Rolling fine-metal-weighted median asking premiums for silver, gold, platinum, palladium, copper, nickel and Goldback, observed from marketplace listings.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "metal": "<metal>"
    },
    "name": "get_observed_premiums"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoProduct page size. Without a query, pages browse the most-listed products.
metalYesWhich metal's observed premiums to return.
queryNoCase-insensitive product label/canonical-key search.
cursorNoOpaque continuation token returned by the same tool with exactly the same filters.

Output Schema

NameRequiredDescriptionDefault
asOfYesUTC latest observation instant.
metalYes
overallYes
productsYes
sourceUrlYes
categoriesYes
nextCursorYes
windowDaysYes
productOrderYesHow product rows were selected: search (query match, catalog order) or listing_count (browse, most-listed first). Empty products means no data.
productQueryYes
minimumListingsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedOutput schema / properties / categories / items / title
      Added value: +"PremiumCategory"
    • changedOutput schema / properties / overall / anyOf
      Previous value: -[
      -  {
      -    "additionalProperties": false,
      -    "properties": {
      -      "listingCount": {
      -        "minimum": 0,
      -        "type": "integer"
      -      },
      -      "medianPercent": {
      -        "type": "number"
      -      }
      -    },
      -    "required": [
      -      "medianPercent",
      -      "listingCount"
      -    ],
      -    "type": "object"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "additionalProperties": false,
      +    "properties": {
      +      "listingCount": {
      +        "minimum": 0,
      +        "type": "integer"
      +      },
      +      "medianPercent": {
      +        "type": "number"
      +      }
      +    },
      +    "required": [
      +      "medianPercent",
      +      "listingCount"
      +    ],
      +    "title": "PremiumSummary",
      +    "type": "object"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • addedOutput schema / properties / products / items / title
      Added value: +"PremiumProduct"
  2. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnly, openWorld and non-destructive, so the safety profile is covered. The description adds genuine methodology context (median, fine-metal-weighted, marketplace listings, rolling), but leaves 'rolling' undefined (no window length or update cadence) and says nothing about result shape or how listing coverage is sampled.

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?

A single front-loaded sentence with no filler; every clause carries information. It is dense with jargon ('fine-metal-weighted', 'rolling') that is never unpacked, which slightly hurts immediate comprehension.

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?

Output schema exists, so return-value explanation is not required, and the annotations plus description cover safety and metric definition. The residual gap is that the description reads as an aggregate median while the schema's limit/query parameters page over individual products, leaving the result granularity ambiguous.

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 metal, limit, query and cursor are already fully documented in the schema, giving a baseline of 3. The description adds no parameter-level meaning of its own, such as whether query filters which products the median is computed over.

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 names the exact metric (rolling fine-metal-weighted median asking premium) and enumerates the covered metals, so an agent knows precisely what data comes back and can distinguish it from get_spot_prices and get_price_history. It never explicitly contrasts itself with those siblings, so it stops short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use or when-not-to-use guidance, no mention of picking this over get_spot_prices/get_price_history, and no hint about paginating with cursor or narrowing with query. Usage is only inferable from the phrase 'premiums over spot'.

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