Skip to main content
Glama

Ranking volatility by country

keyword_metrics_volatility_worldwide
Read-only

Ranking-algorithm volatility for one date across every country, so you can tell a global store change from a local one. Costs 12 credits.

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": {
      "store": "<store>"
    },
    "name": "keyword_metrics_volatility_worldwide"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoDay to report on, YYYY-MM-DD. Defaults to the latest.
limitNoHow many countries to return, up to 250. 50 by default.
storeYesWhich app store: "android" (Google Play) or "ios" (App Store).
windowNoDays to average over.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already establish read-only and open-world behavior. The description adds the important operational fact of 12-credit cost and the one-date/worldwide scope, though it does not define how volatility is computed or returned.

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?

Two sentences, front-loaded with the purpose and followed by cost. No filler; both sentences earn their place.

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 worldwide metrics call with fully documented parameters and safety annotations, the description supplies enough to select and invoke it. It leaves the output shape undefined because no output schema exists, which is a minor gap.

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 date, limit, store, and window are already documented in the schema. The description mentions only the one-date aspect and adds no syntax or default details beyond 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 resource and scope: ranking-algorithm volatility for a single date across every country. The worldwide scope distinguishes it from keyword_metrics_volatility, but the description does not name that sibling explicitly.

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?

Gives a clear selection context—use it to distinguish a global store change from a local one—and adds credit cost. It does not state exclusions or explicitly route single-country queries to keyword_metrics_volatility.

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.