MAScope MCP Server

get_category_analytics

Get a breakdown of all World MiniApp categories with app count, weekly users, and top 3 apps per category to understand the ecosystem landscape.

Instructions

Get a breakdown of all World MiniApp categories with app count, total weekly users, and top 3 apps per category. Useful for understanding the MiniApp ecosystem landscape.

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_category_analytics"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.1Aug 4, 2026

TDQS

A4.5/5.0

Behavior4/5

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

With no annotations, the description carries the burden of disclosing behavior. It clearly states the output contents (app count, total weekly users, top 3 apps per category), implying a read-only aggregate operation. It does not mention data freshness, sorting, or potential limitations, but for a simple analytics tool this is adequate.

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, no redundancy, front-loaded with the primary action and outcome. Every word contributes to understanding the tool's purpose and value.

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

Completeness5/5

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

Given the tool's simplicity (no parameters, no output schema, no nested objects), the description is complete. It specifies the returned breakdown, and sibling tools clearly cover different use cases, so no missing context is evident.

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?

The tool has zero parameters, so there is nothing to explain. The baseline for 0 parameters is 4, and the description appropriately focuses on the output rather than parameter details.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb ('Get') and clearly identifies the resource: a breakdown of all World MiniApp categories, including app count, total weekly users, and top 3 apps per category. This distinguishes it from sibling tools like get_app_details or search_miniapps, which focus on individual apps.

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

Usage Guidelines4/5

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

It provides a clear usage context: 'Useful for understanding the MiniApp ecosystem landscape.' While it doesn't explicitly contrast with alternatives, the context implies this tool is for high-level category analytics rather than individual app lookups. A more explicit comparison would warrant a 5.

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

Deploy Server