Skip to main content
Glama

compare_matrix

Compare App Store competitors across multiple niche keywords, deduplicate overlapping apps, and cluster 1–3 star review pain points into a bilingual heatmap.

Instructions

[PRO] Multi-keyword deduplicated App Store competitor matrix + bilingual 1-3 star pain-point clustering heatmap. Requires a valid OPC1. license key (store-radar-mcp or *).

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": {
      "keywords": "<keywords>"
    },
    "name": "compare_matrix"
  }
}

Input Schema

NameRequiredDescriptionDefault
countryNo2-letter App Store storefront codeus
keywordsYesList of related niche keywords to cross-compare and deduplicate
license_keyNoOptional inline OPC1.<payload>.<sig> Pro license token
use_fixtureNoUse deterministic offline fixture dataset
limit_per_keywordNoCompetitors per keyword (1-10)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses PRO gating, the OPC1 license requirement, deduplication, and bilingual pain-point clustering, but it does not clarify read-only behavior, error handling for invalid licenses, rate limits, or the shape of the returned matrix and heatmap.

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?

It is compact and front-loaded, with no filler. The phrasing is dense and noun-heavy, but it conveys the core outputs and license requirement efficiently.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a five-parameter, no-annotation, no-output-schema tool that produces a matrix and heatmap, the description is too sparse. It states the artifacts and license gate but omits usage alternatives, output format, error behavior, and operational constraints an agent would need to invoke it confidently.

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 all five parameters are already documented in the input schema. The description adds only indirect meaning around multi-keyword comparison and licensing, not parameter-level semantics beyond what the schema provides.

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 a specific resource and output: a multi-keyword deduplicated competitor matrix plus a bilingual 1-3 star pain-point clustering heatmap. It is clear enough to distinguish a cross-keyword comparison from a single-keyword probe or a battlecard, but it does not explicitly differentiate itself from the listed siblings.

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?

The description implies usage through 'multi-keyword' and 'cross-compare', but gives no explicit when-to-use, when-not-to-use, or alternative guidance. It does not explain when an agent should call compare_matrix versus generate_battlecard or probe_keyword.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools