Skip to main content
Glama

Mobile vitals

get_mobile_vitals
Read-only

The mobile app's vitals from real devices: cold (and warm) app start, time to initial display (ttid) and full display (ttfd), slow and frozen frame percentages, and JS stall time; overall, per screen (busiest first) and per release. Each with p50, p75, p95 and the sample count. platform ios, android or both (default).

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

Input Schema

NameRequiredDescriptionDefault
toNoAn ISO time, or how long ago (default now)
fromNoAn ISO time, or how long ago: 30m, 24h, 7d
rangeNoWindow: 1h, 24h, 7d, 14d, 30d or 90d (default 24h). Ignored when from is given.
sourceNobackend (servers), frontend (app and web), or all (default)
releaseNoOnly this release: 2.0.77+185, 2.0.77 (every build) or package@2.0.77+185
serviceNoOnly this service, like house-ai-api or the app's bundle id
platformNo
environmentNoLike production. Default: production when the app has it, else its busiest non-development one. 'all' for every environment.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / release / description
      Previous value: -"Only this release (service version)"New value: +"Only this release: 2.0.77+185, 2.0.77 (every build) or package@2.0.77+185"
  2. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds useful output-shape context (percentiles p50/p75/p95 plus sample count, breakdowns ordered busiest-first), but says nothing about latency, result-size limits, or how sparse data is handled.

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?

A single dense sentence with semicolon-separated metric groups, front-loaded with the resource and followed by breakdowns and statistics. Every clause carries information, though the run-on style and unexplained jargon (ttid/ttfd) cost a point.

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?

With no output schema and eight optional parameters, the description does the important work of describing what comes back: metric set, aggregation levels, and percentile/sample-count shape. It is not fully complete on filtering interaction (range vs from) or on what an empty or low-sample result looks like, but it is sufficient to call the tool correctly.

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 88%, so the schema already documents from/to, range, source, release, service and environment including defaults. The description's only parameter contribution is spelling out the platform values 'ios, android or both (default)', which the schema enum lists without any prose. That is a real but small addition, so the 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?

The description names a specific resource and enumerates the exact metrics returned (cold/warm start, ttid, ttfd, slow/frozen frame percentages, JS stall time) plus the breakdown dimensions (overall, per screen, per release). An agent knows precisely what data this yields. It stops short of a 5 because it never names the obvious sibling get_web_vitals or otherwise states what it is not.

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: an agent can infer this is the mobile-app performance tool because of 'real devices' and the mobile-specific metrics. There is no explicit when-to-use, no exclusion against get_web_vitals or get_performance_overview, and no note on prerequisites such as whether the app must be instrumented.

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