Skip to main content
Glama
billylo1

aptabase-mcp

by billylo1
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_top_regions

Retrieve top geographic regions by unique session count for your app. Filter by period, OS, event, or version to analyze regional engagement.

Instructions

Top regions by unique sessions for the period.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
appIdYesAptabase app id (from list_apps)
osNameNoFilter by OS name (e.g. iOS, Android, macOS)
periodNoDashboard period preset. Prefer this over startDate/endDate. Defaults to 24h for stats tools when neither period nor dates are set.
endDateNoISO end datetime (use with startDate if not using period)
buildModeNoRelease or debug build mode (debug queries appId_DEBUG)release
eventNameNoFilter by event name
startDateNoISO start datetime (use with endDate if not using period)
appVersionNoFilter by app version
countryCodeNoFilter by ISO country code
deviceModelNoFilter by device model
granularityNoOverride bucket size; auto-derived from period/range when omitted

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.8/5.0
Behavior1/5

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

No annotations are provided, so the description carries the full burden. It only restates the basic function without disclosing default period behavior, result limits, sorting order, or interaction with filters. This is insufficient for an agent to predict side effects or output characteristics.

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?

The description is a single, front-loaded sentence with no fluff. It conveys the essential purpose in a compact form, though it does not include additional context.

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

Completeness1/5

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

With 11 parameters, no output schema, and no annotations, the description is far too minimal. It omits return format, default period, the meaning of 'unique sessions', and how filters affect results, making the tool under-documented for an agent.

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 fully documents all 11 parameters. The description adds no parameter-level meaning beyond what the schema provides, hence the baseline score of 3.

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 clearly states the resource ('regions') and metric ('unique sessions') with a time scope ('for the period'). It distinguishes from sibling tools like get_top_countries by focusing on regions rather than countries.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives such as get_top_countries or get_top_devices. It does not mention any exclusions, prerequisites, or common scenarios.

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

Deploy Server

Other Tools