Skip to main content
Glama

DECA Labs

Demand signals

get_signals
Read-only

Today's demand patterns from DECA's radar: groups of apps climbing the App Store and Google Play charts, with what people say and want about them and the public posts behind it. Every chart fact names its store category and country. Free. Updated daily.

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

Input Schema

NameRequiredDescriptionDefault
heatNoOnly patterns people are talking about this much. Optional.
limitNoHow many to return, 1 to 25. Default 10.
queryNoWords that must all appear in the pattern, its apps or what people say. Optional.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/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 safety is covered; the description still adds genuine context beyond them: the data source (DECA's radar), the freshness cadence (updated daily), the absence of cost ('Free'), and the shape of returned facts (each chart fact carries its store category and country). Nothing contradicts the annotations.

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 short sentences, front-loaded with the resource and its scope, then freshness and cost. The fragment 'Free.' is terse but earns its place as a cost signal; overall there is little waste, though the phrasing is slightly promotional rather than operational.

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?

There is no output schema, so the description must carry the return-shape burden, and it does partially: it states that patterns come with quotes, wants, underlying public posts, and store category/country per chart fact. Missing is any hint of result ordering, pagination, or what an empty result means, but for a zero-required-parameter read tool this is close to complete.

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%, with heat's enum and limit's 1-25 bounds all documented in the schema, so the baseline is 3. The description adds no per-parameter meaning — it never explains what 'heat', 'limit' or 'query' match against, though 'what people say and want' loosely hints at the text that query searches.

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 concrete resource with real scope: groups of apps climbing the App Store and Google Play charts, plus the quotes and public posts around them. That is far more specific than the tool name 'get_signals' alone. It does not differentiate itself from any sibling (e.g. get_ideas), but its content is distinctive enough that confusion is unlikely.

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 only implied: 'Today's demand patterns' plus 'Updated daily' suggests you call it to see current, fresh trend data and can re-call it daily rather than relying on cached results. There is no explicit when-to-use statement, no exclusion, and no named alternative among get_ideas / get_my_ideas. 'Free' hints at cost considerations but does not route the agent anywhere.

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