Skip to main content
Glama

featuring_history

Read-only

Use this when you need when and where apps were featured, per app or home shelf, over up to 90 days. Do not use for current shelf order; use charts_get.

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": {
      "store": "<store>"
    },
    "name": "featuring_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
atNoPast time: ISO-8601 or -24h, -7d.
appNoListing ref or OpenApps URL.
chartNoChart name; stores_get lists them.
limitNo
sinceNoWindow start: ISO-8601 or -24h, -7d.-24h
storeYes
cursorNo
regionNoChatGPT country code (default us).
contextNoThe user's goal, briefly.
response_formatNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / store / enum
      Previous value: -[
      -  "chatgpt",
      -  "claude",
      -  "cursor",
      -  "grokbot",
      -  "perplexity"
      -]New value: +[
      +  "chatgpt",
      +  "claude",
      +  "cursor",
      +  "grokbot",
      +  "perplexity",
      +  "muse"
      +]
  2. Changed1 schema field changed
    • changedInput schema / properties / store / enum
      Previous value: -[
      -  "chatgpt",
      -  "claude",
      -  "cursor",
      -  "grokbot"
      -]New value: +[
      +  "chatgpt",
      +  "claude",
      +  "cursor",
      +  "grokbot",
      +  "perplexity"
      +]
  3. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered; the description adds the meaningful behavioral constraint of a 90-day lookback window and the two modes of aggregation (per app vs. home shelf). It omits pagination behavior despite a cursor parameter, and says nothing about result size or rate limits, so it is strong but not complete.

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

Conciseness5/5

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

Two sentences, zero filler, with the intended use stated first and the routing exclusion second. Nothing in it could be removed without losing information.

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

Completeness3/5

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

For a 10-parameter read tool with no output schema and only 60% schema coverage, the description covers scope and the time window but leaves pagination (cursor/limit) and several result-shaping parameters unexplained. An agent could call it correctly for the common case but would be guessing on paging and output format.

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 60% across 10 parameters. The description indirectly motivates the app and chart parameters via "per app or home shelf" and explains the time bound that governs since/at, but it adds no meaning for limit, cursor, region, context, or response_format. With the schema already documenting most of what matters, the baseline 3 with modest added value is right.

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 resource and scope: featured history (when and where apps were featured), segmented by app or home shelf, bounded to 90 days. That is far more than a restatement of the name and an agent can tell it apart from charts_get. It stops short of 5 only because the verb is phrased indirectly ("when you need when and where") rather than as a crisp operation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives both a positive condition (historical featuring over up to 90 days) and an explicit exclusion with a named alternative: "Do not use for current shelf order; use charts_get." That is the exact when/when-not/alternative pattern, leaving nothing to inference.

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