Skip to main content
Glama
Sign In

Fledly

by app.fledly
OverviewDiscussionsAdmin

Compare my app with its competitors

get_competitor_report
Read-onlyIdempotent

For one of the user's tracked apps in one country: each competitor's recent App Store listing changes (name, subtitle, icon, screenshots, price, version, description), ratings gained, competitor positions on the user's tracked searches with gaps (a competitor in the top 10 where the user is not), words competitors use in their name or subtitle that the user's app does not, top-10 newcomers and drop-outs over about 7 days, and apps often in the user's top 10 that could be added as competitors.

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": {
      "app_id": "<app_id>"
    },
    "name": "get_competitor_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoHow many days of changes to include.
app_idYesApp Store id of a tracked app.
countryNoOne of the app's tracked countries; default is its main store.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/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. Beyond that, the description enumerates the report's sections and mentions a roughly 7-day window for top-10 movement, but it does not explain output format, data freshness, or how the days parameter affects each section.

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

Conciseness3/5

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

The content is relevant and front-loaded with scope, but it is delivered as one long run-on sentence with nested parentheticals. A segmented or bulleted structure would make the many report sections easier to scan.

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?

With no output schema, the description does a good job enumerating the report contents, which is the main completeness need. It still leaves output format and the precise interaction between days and the 'about 7 days' top-10 window unclear, but it is sufficient for an agent to decide whether to call it.

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 the schema already documents all three parameters. The description reinforces that app_id is a tracked app and country is one of its tracked countries, but adds no new syntax, format, 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?

The title and description identify a specific report covering competitor listing changes, ratings, tracked-search positions, gaps, shared words, top-10 movement, and candidate competitors, scoped to one tracked app and country. It is clearly distinct from simple getters like get_app or get_top_charts, though it does not explicitly name a sibling alternative.

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 implies usage context by requiring one of the user's tracked apps and one country, but it does not explicitly say when to choose this tool over alternatives such as get_app, check_metadata, get_top_charts, or track_competitor, nor does it state exclusions.

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

All Fledly toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources