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

app-store-connect-mcp

by devinwang
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

game_center_matchmaking_rule_sets_get_collection

Retrieve a list of Game Center matchmaking rule sets from App Store Connect to configure matchmaking rules, teams, and queues for your app.

Instructions

GET /v1/gameCenterMatchmakingRuleSets (GET /v1/gameCenterMatchmakingRuleSets)

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": "game_center_matchmaking_rule_sets_get_collection"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNomaximum resources per page
includeNocomma-separated list of relationships to include
limit_rulesNomaximum number of related rules returned (when they are included)
limit_teamsNomaximum number of related teams returned (when they are included)
limit_matchmakingQueuesNomaximum number of related matchmakingQueues returned (when they are included)
fields_gameCenterMatchmakingRulesNothe fields to include for returned resources of type gameCenterMatchmakingRules
fields_gameCenterMatchmakingTeamsNothe fields to include for returned resources of type gameCenterMatchmakingTeams
fields_gameCenterMatchmakingQueuesNothe fields to include for returned resources of type gameCenterMatchmakingQueues
fields_gameCenterMatchmakingRuleSetsNothe fields to include for returned resources of type gameCenterMatchmakingRuleSets

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

C2.2/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 behavioral burden, and it discloses almost nothing. The bare 'GET' implies a safe read, but pagination behavior, default page size, relationship-inclusion cost, and authorization requirements are all unstated.

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 the brevity comes from saying nothing rather than from efficient editing, and the path is duplicated inside the parentheses for no benefit. There is no front-loaded statement of what the tool returns or does.

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 nine-parameter endpoint with sparse fieldsets, relationship inclusion, and per-relationship limits, plus no output schema and no annotations, the description explains none of the non-obvious usage. An agent must reverse-engineer the pagination and inclusion model entirely from the schema.

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%, with all nine parameters (limit, include, limit_*, fields_*) documented inline in the schema, so the baseline is 3. The description adds nothing beyond the schema, but it does not need to.

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 literally the HTTP method and path repeated twice, which is a restatement of the tool name rather than an explanation of purpose. It does convey that this is a read/list endpoint for Game Center matchmaking rule sets, but an agent gets no more than it could infer from the identifier itself.

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 guidance on when to call this collection endpoint versus the sibling get_instance, or when to prefer a related-resource endpoint such as rule_sets_rules_get_to_many_relationship. The 'collection' in the name weakly implies a bulk listing, but nothing is stated.

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