Skip to main content
Glama
Sign In
app-store-connect-mcp

app-store-connect-mcp

by devinwang
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

game_center_app_versions_get_instance

Fetch a Game Center app version by ID and optionally include related compatibility and App Store version data for inspection.

Instructions

GET /v1/gameCenterAppVersions/{id} (GET /v1/gameCenterAppVersions/{id})

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": {
      "id": "<id>"
    },
    "name": "game_center_app_versions_get_instance"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesthe id of the requested resource
includeNocomma-separated list of relationships to include
fields_appStoreVersionsNothe fields to include for returned resources of type appStoreVersions
limit_compatibilityVersionsNomaximum number of related compatibilityVersions returned (when they are included)
fields_gameCenterAppVersionsNothe fields to include for returned resources of type gameCenterAppVersions

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

D1.7/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 behavioral burden, yet it discloses nothing: not that this is a read-only single-resource fetch, not error behavior for a bad id, not whether relationship includes affect payload size. A bare path adds zero transparency.

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

Conciseness2/5

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

It is short, but half its content is a redundant parenthetical repetition of the identical path. Brevity here reflects under-specification rather than effective concision, so it does not earn a high mark.

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?

For a 5-parameter tool with no annotations and no output schema, the description must supply the missing context. Instead it supplies none, leaving the agent with no idea what a successful response contains or how the include/fields/limit parameters shape it.

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 already documents id, include, limit_compatibilityVersions and both sparse-fieldset parameters. Per the high-coverage baseline this is a 3; the description adds no meaning beyond the schema.

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

Purpose2/5

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

The description is just the HTTP route 'GET /v1/gameCenterAppVersions/{id}' repeated twice in parentheses. It does convey method and resource path, but it restates the tool name rather than explaining in natural language what the operation retrieves, so it is effectively a tautology.

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

Usage Guidelines1/5

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

There is no statement of when to use this tool, when not to, or which sibling covers the alternative case (e.g. game_center_app_versions_compatibility_versions_get_to_many_relationship for related collections). Nothing routes the agent.

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