Skip to main content
Glama

Get an app

get_app
Read-onlyIdempotent

Read application metadata, the version each store serves (liveVersions; a release still in review is not live) and the last attempted/successful synchronization timestamps. liveVersionName is a legacy single value, Google’s on a two-store app.

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": {
      "appId": "<appId>"
    },
    "name": "get_app"
  }
}

Input Schema

NameRequiredDescriptionDefault
appIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the description correctly spends its words on domain behavior instead: that a release still in review is not counted as live, and that liveVersionName is a legacy single field. These are non-obvious semantics an agent could not derive from structured data. It stops short of saying what happens for an unknown appId.

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

Conciseness3/5

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

Sized well at two sentences with the read scope front-loaded, so it is not padded. However, the second sentence is syntactically broken and reads as a fragment, forcing the agent to parse ambiguity about which store liveVersionName reflects.

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?

With no output schema, the description does useful work naming the returned fields and their caveats, but it omits how appId is obtained/validated and says nothing about failure behavior for a missing app. Adequate for a simple read tool, but not whole.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and the single required parameter appId is never mentioned in the description — no format, no indication that it is the internal app identifier returned by list_apps. With one required param and no schema documentation, the description should have compensated.

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?

Opens with a specific verb and resource ('Read application metadata') and enumerates the notable fields returned (liveVersions, sync timestamps, legacy liveVersionName), which distinguishes it from list_apps and get_app_metrics. The final clause ('Google's on a two-store app') is garbled and blunts the clarity of the liveVersionName note, but the core purpose is unmistakable.

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?

There is no explicit statement of when to call this versus list_apps, get_app_metrics, get_sync_job, or check_apple_release, even though several siblings overlap on app/version/sync data. Usage is only inferable from the tool's name and the fact that appId is required.

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