Skip to main content
Glama

Explain a keyword score

score_keyword_explain
Read-onlyIdempotent

Explain one keyword's modeled scores: popularity (autocomplete A, ratings R), difficulty (ratings Rt, title match T, quality Q, big publishers B), relevance to an application (lexical L, competitors C, embedding E) and opportunity, with the top apps and store suggestions. Popularity, difficulty, relevance and opportunity are modeled 0-100 indexes, not store-reported search volume. Read-only: answered from the cache when possible, otherwise one cached store check (a small daily allowance); it never spends a monthly run. Runs on ASOClimb's servers; no AI or store access is needed on your side.

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": {
      "keyword": "<keyword>"
    },
    "name": "score_keyword_explain"
  }
}

Input Schema

NameRequiredDescriptionDefault
storeNoStore (default apple_app_store).
countryNoISO country code (default US).
keywordYesKeyword.
languageNoLanguage code (default: the storefront's own).
application_idNoOptional: score relevance against this tracked application (its store and country are the defaults).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior5/5

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

Goes well past the annotations by disclosing the cost model: cache-first, at most one cached store check under a small daily allowance, and never a monthly run. It also pre-empts a likely misinterpretation by stating the 0-100 indexes are modeled, not store-reported search volume, and that no AI or store access is needed client-side.

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-loaded with the core explanation content, followed by the modeling caveat and then the cost/read-only statement — a sensible order with no filler. The dense parenthetical letter codes (A, R, Rt, T, Q, B, L, C, E) are cryptic and could have been dropped without loss.

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?

Covers what is explained, that the indexes are modeled rather than measured, and the cost/read-only profile, which is enough for an agent to call it correctly with five fully described parameters and no output schema. Minor gaps remain around failure modes or what happens when a keyword is unscored in the chosen store/country.

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 coverage is 100%, so each of the five parameters is already documented, including application_id scoring relevance against a tracked app. The description reinforces what 'relevance' means conceptually but adds no parameter-level syntax, defaults, or interaction rules beyond the schema, making the baseline of 3 appropriate.

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 resource: 'Explain one keyword's modeled scores', then enumerates the four score families (popularity, difficulty, relevance, opportunity) plus the accompanying top apps and store suggestions. That enumeration distinguishes it from list_keyword_opportunities and get_keyword_inspection in substance, though no sibling is named explicitly.

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?

Usage is implied rather than stated: an agent can infer this is the per-keyword drill-down for a modeled score. There is no explicit 'use this when / use X instead' routing against siblings such as get_keyword_inspection or list_keyword_opportunities, so the agent must infer the boundary.

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