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

app-store-connect-mcp

by devinwang
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

game_center_challenge_images_get_instance

Retrieve a Game Center challenge image by its ID to access file details, upload operations, or asset delivery state. Specify fields to include for a focused response.

Instructions

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

Input Schema

NameRequiredDescriptionDefault
idYesthe id of the requested resource
fields_gameCenterChallengeImagesNothe fields to include for returned resources of type gameCenterChallengeImages

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

D1.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 behavioral burden, yet it discloses nothing: no indication that this is a safe read, no authentication or permission requirements, no pagination/sparse-fieldset behavior, and no error semantics for an unknown id. The path string is pure tautology.

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 this is under-specification rather than conciseness, and the content is duplicated twice inside the same sentence. Length is not the problem; there is simply nothing useful to front-load.

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?

For a two-parameter read endpoint with no output schema and no annotations, the description should at minimum state what a game center challenge image is and that it is a read of one existing resource. As written, an agent cannot confirm the resource semantics or expected failure modes.

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% (both 'id' and 'fields_gameCenterChallengeImages' are documented in the schema), so the baseline is 3 even though the description contributes no parameter meaning at all. It neither explains the id format nor the sparse-fieldset usage.

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 a bare restatement of the tool name as a REST path, 'GET /v1/gameCenterChallengeImages/{id}', duplicated verbatim in parentheses. It does technically convey a read of a single gameCenterChallengeImage by id, but adds no vocabulary beyond the name itself and never differentiates this from the many sibling game_center_challenge_images_* tools.

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 guidance whatsoever on when to use this tool, when not to, or which sibling to prefer (e.g., game_center_challenge_localizations_image_get_to_one_related or the list/create/update/delete variants). The agent must infer everything from the name.

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