Skip to main content
Glama
Sign In

Fledly

by app.fledly
OverviewDiscussionsAdmin

List app ideas backed by market data

list_app_ideas
Read-onlyIdempotent

Lists scored iOS app ideas. 'proven' ideas are concepts that several young apps already earn money with; 'search' ideas come from App Store searches with demand and weak competition. Each idea has a score from 0 to 100, a verdict (build, consider or skip) and a one-line summary.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_app_ideas"
  }
}

Input Schema

NameRequiredDescriptionDefault
genreNoApp Store category.
limitNoHow many ideas to return.
queryNoWords to match in the idea title, summary or category.
sourceNoWhich idea list to read.proven
countryNoApp Store country (two-letter code).us
verdictNoOnly ideas with this verdict.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare this a read-only, idempotent, non-destructive, closed-world operation, so the safety profile is covered. The description adds useful content context — the 0-100 score, the verdict taxonomy, and the one-line summary — but says nothing about result ordering, pagination, or what happens when filters match nothing.

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?

Three sentences, front-loaded with the core action and then the domain vocabulary needed to use the source filter correctly. No filler, though the score/verdict/summary sentence is closer to return-value documentation than tool selection guidance.

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 carries the burden of describing returns and does so at a useful level (score range, verdict values, summary). Six optional, fully documented parameters need little extra framing, though a note on default behavior (source defaults to 'proven') would round it out.

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 the baseline is 3, but the description goes beyond the enums by explaining what 'proven' ideas are (concepts several young apps already monetize) versus 'search' ideas (from App Store searches with demand and weak competition). That meaning is not recoverable from the enum values alone.

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 states a specific verb and resource ('Lists scored iOS app ideas') and then defines the two idea categories it can return, which makes the tool's scope concrete. It doesn't explicitly distinguish itself from siblings like get_app_idea or find_young_earners, so it falls short of a 5.

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?

'proven' and 'search' are defined, which implicitly guides source selection when the agent calls it. However, there is no explicit when-to-use guidance, no exclusions, and no pointer to the single-idea sibling get_app_idea or to find_young_earners.

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