Skip to main content
Glama
storelift-mcp

storelift-mcp

New apps on charts

market_new_apps
Read-onlyIdempotent

Find apps entering top charts for the first time, newest first, with publishers and indexed-day coverage to identify emerging market entrants.

Instructions

Apps seen on a top chart for the first time, newest first, with the publisher behind each one. daysCovered says how many of the requested days the index holds, so every first-seen date you read is a day we indexed.

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": "market_new_apps"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNolook back N days, up to 30
limitNorows, up to 200
countryNostorefront code; omit for every storefront

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.5.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive, closed-world behavior, so the bar is lower. The description still adds real context beyond them: result ordering (newest first), inclusion of the publisher per row, and an explicit index-coverage caveat via daysCovered so a missing first-seen date is not misread as 'did not exist'.

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?

Two sentences, no filler, and the core behavior is front-loaded ahead of the caveat. Slight deduction because daysCovered is introduced without saying it lives in the response, which can read as an unexplained term.

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?

No output schema exists, and the description still conveys the key shape of the return: first-seen apps, ordering, and the publisher field, plus the coverage caveat. Minor gaps remain around default values for limit/days and how partial coverage interacts with the limit, but nothing that would cause a wrong call.

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 explains days, limit and country, including bounds. The description touches 'requested days' but the parameter it elaborates, daysCovered, is a response field rather than an input, so it adds little to input meaning. Baseline 3 applies.

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 and non-obvious resource: apps appearing on a top chart for the first time, ordered newest first, with the publisher included. That is clearly distinct from a plain chart listing such as market_charts or get_charts, 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 by the framing (find new chart entrants), but there is no explicit when-to-use guidance, no exclusions, and no pointer to alternatives for someone who wants the full chart rather than first-timers. An agent must infer the routing decision.

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