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

app-store-connect-mcp

by devinwang
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

apps_subscription_grace_period_get_to_one_relationship

Retrieve the subscription grace period relationship for a specific App Store Connect app by ID to manage or audit grace period settings.

Instructions

GET /v1/apps/{id}/relationships/subscriptionGracePeriod (GET /v1/apps/{id}/relationships/subscriptionGracePeriod)

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

Input Schema

NameRequiredDescriptionDefault
idYesthe id of the requested resource

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, and it discloses nothing: no return shape (linkage object vs. full resource), no auth/permission requirements, no error behavior when no grace period exists. Repeating the endpoint URL twice adds no behavioral information.

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 text is short but not concise in any useful sense: the identical path is printed twice inside parentheses, which is pure redundancy with zero informational content and no front-loaded explanation of purpose.

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 parameterless-style GET relationship tool with no annotations and no output schema, the description should at minimum state what the call returns and when the relationship may be absent. It provides none of that, leaving the agent with only a URL to work from.

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% and there is a single required 'id' property already documented as 'the id of the requested resource'. The description adds only the implicit hint that {id} is an app id, so per the high-coverage baseline a 3 is appropriate.

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 verbatim restatement of the tool name's HTTP method and path, duplicated in parentheses with no added wording. It reveals 'GET the subscriptionGracePeriod relationship' only implicitly through the URL, and it does not distinguish this tool from its close sibling apps_subscription_grace_period_get_to_one_related, which differs only by relationship-vs-related semantics.

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 when-to-use guidance, no prerequisite (e.g., needing an existing app id with a grace period configured), and no routing to the alternative sibling variants. The agent is left to infer everything from the path string.

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