Skip to main content
Glama

Spot move check

spot_move_check
Read-onlyIdempotent

Did spot move >= threshold_pct over 1h, 24h or 7d? Current and reference spot with times, change_pct, moved; null with a reason if history is short. Poll only, no alerts. Free; custom: 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": "gold",
      "window": "24h"
    },
    "name": "spot_move_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
metalYesMetal.
windowNoLookback.24h
threshold_pctNoPercent.

Output Schema

NameRequiredDescriptionDefault
currentNo
referenceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior, so the bar is lower. The description still adds real operational context: results can return null with a reason when history is short, it is poll-only with no alerting, and pricing/tiering is noted with a custom contact path. It does not state rate limits or pagination, but no pagination applies here.

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

Conciseness5/5

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

Three short, front-loaded fragments with zero filler: the core question first, then output/failure shape, then usage constraint and commercial terms. Telegraphic style costs almost nothing in readability while packing a lot of information.

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?

An output schema exists, so return values need only light coverage, which the description supplies via field names (current/reference spot, times, change_pct, moved). The short-history null case is disclosed, which is the main edge behavior an agent needs. Minor gap: no pointer to which sibling to use for alerts or raw price series.

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% and both enum parameters are self-documenting, so the baseline of 3 applies. The description restates the window options and threshold comparison already encoded in the schema, adding marginal interpretation (windows are lookbacks, threshold is a percent move) but no new syntax or defaults guidance.

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 states the specific computation in question form: whether spot moved at least threshold_pct across 1h/24h/7d windows, with current and reference spot values. That is a concrete verb+resource, and 'spot move check' is distinguishable from generic price lookups like get_spot_prices. It does not name a sibling for contrast, which keeps it out of the top score.

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?

'Poll only, no alerts' usefully rules out a push/alert mode and implicitly steers toward the alert sibling for notification needs, but no explicit guidance is given on when to pick this over get_spot_prices, premium_over_spot, or get_price_history. Usage is implied by the threshold framing rather than stated.

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