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

app-store-connect-mcp

by devinwang
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

game_center_challenge_localizations_get_instance

Fetch a Game Center challenge localization by ID, with options to include related version and image details.

Instructions

GET /v1/gameCenterChallengeLocalizations/{id} (GET /v1/gameCenterChallengeLocalizations/{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_challenge_localizations_get_instance"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesthe id of the requested resource
includeNocomma-separated list of relationships to include
fields_gameCenterChallengeImagesNothe fields to include for returned resources of type gameCenterChallengeImages
fields_gameCenterChallengeVersionsNothe fields to include for returned resources of type gameCenterChallengeVersions
fields_gameCenterChallengeLocalizationsNothe fields to include for returned resources of type gameCenterChallengeLocalizations

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

C2/5.0
Behavior2/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. The GET verb weakly implies a read operation, but nothing is said about permissions, error behavior, or whether the resource is returned in full.

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?

The only content is the endpoint path, and it is redundantly repeated twice inside the same string. Short, but the duplication means zero information is front-loaded beyond what the name already implies.

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

Completeness2/5

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

With no annotations, no output schema, and a description that is just a path, an agent has no context about the returned resource shape or the purpose of this fetch. Relying entirely on a fully covered schema leaves the definition barely adequate.

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 all five parameters (id, include, three fields_* filters) are already documented in the schema. The description adds nothing beyond the path template, which merely repeats the required id parameter.

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 only the HTTP path 'GET /v1/gameCenterChallengeLocalizations/{id}', duplicated in parentheses. It restates the tool name rather than explaining what a game center challenge localization is or how it differs from siblings like game_center_challenge_localizations_image_get_to_one_relationship.

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?

No guidance whatsoever on when to use this tool versus the many sibling get/create/update/delete localization tools. No prerequisites, no exclusions, no alternatives named.

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