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

app-store-connect-mcp

by devinwang
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

ci_mac_os_versions_get_instance

Retrieve details for a specific Xcode Cloud macOS version by ID, optionally including related Xcode versions, to inspect available build environments.

Instructions

GET /v1/ciMacOsVersions/{id} (GET /v1/ciMacOsVersions/{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": "ci_mac_os_versions_get_instance"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesthe id of the requested resource
includeNocomma-separated list of relationships to include
limit_xcodeVersionsNomaximum number of related xcodeVersions returned (when they are included)
fields_ciMacOsVersionsNothe fields to include for returned resources of type ciMacOsVersions
fields_ciXcodeVersionsNothe fields to include for returned resources of type ciXcodeVersions

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

D1.9/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 beyond the raw route: no note about read-only semantics, permissions, error behavior for a missing id, or relationship-inclusion effects. The 'GET' prefix implies a read but that is incidental to the path string.

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 largely wasted: the identical route string is printed twice with no additional content, so it is duplicative rather than efficiently front-loaded.

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?

This is a 5-parameter tool with no annotations and no output schema, and the description is a bare path. An agent gets no sense of what a macOS CI version record contains, how include/fields interact, or what the response looks like.

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 every parameter documented (id, include, limit_xcodeVersions, fields_*). The description adds nothing beyond the schema, so the baseline of 3 applies.

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/ciMacOsVersions/{id}' repeated twice in parentheses. It names a resource and implies a fetch-by-id, but it restates the tool name rather than describing what is retrieved or how it differs from siblings like ci_mac_os_versions_get_collection.

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?

No guidance on when to use this tool versus ci_mac_os_versions_get_collection or ci_mac_os_versions_xcode_versions_get_to_many_relationship. The route pattern hints at single-resource retrieval, but no conditions or alternatives are 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