Skip to main content
Glama

get_snapshot

Read-onlyIdempotent

PAID ($0.02). Snapshot of every series for every country in one call. Pass api_key if you have one (instant card checkout at /pricing); otherwise the response explains how to pay via x402. Every AU series is free to try. After a 200, bind get_changes (free poll) or register_alert (HMAC push; Register: $0 · Delivery after trial: $0.05) on this series so a later gazette does not silently retire the value.

Input Schema

NameRequiredDescriptionDefault
api_keyNoAPI key

Output Schema

NameRequiredDescriptionDefault
errorNoPresent on a free refusal or error; no charge
resultNoOne entry per country; every series value carries confidence_label, coverage_label and label_basis
countriesNo
no_chargeNo
price_usdNo
disclaimerNo
how_to_payNo
bind_seriesNo
explanationNo
x_next_bindNo
http_endpointNo
payment_requiredNotrue when the call needs payment; how_to_pay explains x402 or card

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • removedOutput schema / properties / result / items / properties / series / items / properties / label_basis / properties / source_type / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / result / items / properties / series / items / properties / label_basis / properties / source_type / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / result / items / properties / series / items / properties / label_basis / properties / verification_age_days / anyOf
      Removed value: -[
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / result / items / properties / series / items / properties / label_basis / properties / verification_age_days / type
      Added value: +[
      +  "number",
      +  "null"
      +]
  2. Changed1 schema field changed
    • addedOutput schema / properties / result
      Added value: +{
      +  "description": "One entry per country; every series value carries confidence_label, coverage_label and label_basis",
      +  "items": {
      +    "additionalProperties": {},
      +    "properties": {
      +      "country": {
      +        "type": "string"
      +      },
      +      "series": {
      +        "items": {
      +          "additionalProperties": {},
      +          "properties": {
      +            "confidence": {},
      +            "confidence_label": {
      +              "description": "Evidence verdict derived from source type, verification age and the stale flag (answers: the weakest series read). Rules at /label-rules",
      +              "enum": [
      +                "high",
      +                "medium",
      +                "low"
      +              ],
      +              "type": "string"
      +            },
      +            "country": {
      +              "type": "string"
      +            },
      +            "coverage_label": {
      +              "description": "How much of the question is covered: ready = complete; partial = held with a disclosed limitation or default; gap = no number served. Rules at /label-rules",
      +              "enum": [
      +                "ready",
      +                "partial",
      +                "gap"
      +              ],
      +              "type": "string"
      +            },
      +            "effective_from": {},
      +            "label_basis": {
      +              "additionalProperties": {},
      +              "description": "Inputs and the rule ids that produced the two labels",
      +              "properties": {
      +                "confidence_reasons": {
      +                  "items": {
      +                    "type": "string"
      +                  },
      +                  "type": "array"
      +                },
      +                "coverage_reasons": {
      +                  "items": {
      +                    "type": "string"
      +                  },
      +                  "type": "array"
      +                },
      +                "inputs": {
      +                  "items": {},
      +                  "type": "array"
      +                },
      +                "rules": {
      +                  "type": "string"
      +                },
      +                "rules_version": {
      +                  "type": "string"
      +                },
      +                "source_type": {
      +                  "anyOf": [
      +                    {
      +                      "type": "string"
      +                    },
      +                    {
      +                      "type": "null"
      +                    }
      +                  ]
      +                },
      +                "stale": {
      +                  "type": "boolean"
      +                },
      +                "verification_age_days": {
      +                  "anyOf": [
      +                    {
      +                      "type": "number"
      +                    },
      +                    {
      +                      "type": "null"
      +                    }
      +                  ]
      +                }
      +              },
      +              "type": "object"
      +            },
      +            "last_confirmed": {},
      +            "notes": {},
      +            "series": {
      +              "type": "string"
      +            },
      +            "source": {},
      +            "stale": {
      +              "type": "boolean"
      +            },
      +            "unit": {},
      +            "value": {}
      +          },
      +          "type": "object"
      +        },
      +        "type": "array"
      +      }
      +    },
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
  3. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "http://json-schema.org/draft-07/schema#",
      +  "additionalProperties": {},
      +  "description": "Every series for every country of this brand",
      +  "properties": {
      +    "bind_series": {},
      +    "countries": {},
      +    "disclaimer": {},
      +    "error": {
      +      "description": "Present on a free refusal or error; no charge"
      +    },
      +    "explanation": {},
      +    "how_to_pay": {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    "http_endpoint": {
      +      "type": "string"
      +    },
      +    "no_charge": {
      +      "type": "boolean"
      +    },
      +    "payment_required": {
      +      "description": "true when the call needs payment; how_to_pay explains x402 or card",
      +      "type": "boolean"
      +    },
      +    "price_usd": {
      +      "type": "number"
      +    },
      +    "x_next_bind": {}
      +  },
      +  "type": "object"
      +}
  4. First observed

TDQS

A4/5.0
Behavior5/5

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

Goes well beyond the annotations (which only cover readOnly/idempotent/openWorld) by disclosing the pricing model ($0.02, plus $0.05 alert delivery after trial), the payment/auth flow (api_key, card checkout vs x402 fallback), the AU trial scope, and the data-lifecycle risk that a gazette may retire an unbound value. This is unusually rich behavioral context for a paid read tool.

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-loads the price and purpose, then proceeds to auth and follow-up routing. Dense but mostly earns its place, though the final sentence packs HMAC, trial pricing, and a gazette-lifecycle warning into one clause, slightly straining readability.

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 and annotations cover the safety profile, so the description is not obligated to explain return values. It completes the picture with pricing, auth fallback, and next-step tooling; the only minor omission is an explicit contrast with the single-series fetch siblings.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3. The description adds meaning beyond 'API key' by clarifying it is optional ('Pass api_key if you have one') and describing the fallback behavior (the response explains how to pay via x402) when it is omitted. That is genuine value over the 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?

States a specific verb and scope: 'Snapshot of every series for every country in one call.' This is distinguishable from siblings like get_series, list_series, and get_series_history because it fetches everything in one bulk call. However, it does not explicitly frame itself against those siblings, so the differentiation is inferred from scope rather than stated.

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?

The description gives strong guidance on what to do AFTER a 200, routing between get_changes ('free poll') and register_alert ('HMAC push'). But for this tool itself, the when-to-use is only implied by 'in one call' rather than stated against alternatives like get_series or list_series. Adequate but with a clear gap on the primary selection decision.

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