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

app-store-connect-mcp

by devinwang
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

app_encryption_declarations_app_get_to_one_related

Fetch the App Store Connect app record linked to a specific app encryption declaration ID.

Instructions

[DEPRECATED] GET /v1/appEncryptionDeclarations/{id}/app (GET /v1/appEncryptionDeclarations/{id}/app)

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

Input Schema

NameRequiredDescriptionDefault
idYesthe id of the requested resource
fields_appsNothe fields to include for returned resources of type apps

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

C2.5/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full behavioral burden. It discloses only that this is a deprecated GET endpoint; it says nothing about authentication, permissions, pagination, response shape, or the effect of the fields_apps parameter.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short and front-loads the deprecation warning, which is good. However, it is excessively terse and repeats the same endpoint path twice in parentheses, adding redundant text without adding information.

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?

Given no output schema and no annotations, an agent still lacks basic operational context such as what the related app object contains and how this differs from the sibling relationship endpoint. The deprecation note is helpful but insufficient for confident invocation.

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 the schema already documents the id and fields_apps parameters thoroughly. The description adds no parameter meaning, so the baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description identifies a GET on the appEncryptionDeclarations/{id}/app path, so the resource and operation are inferable. However, it is only a raw endpoint path with no natural-language statement, and it does not distinguish this tool from the sibling app_encryption_declarations_app_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 Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The only guidance is the [DEPRECATED] marker, which usefully signals the tool should be avoided. But it gives no condition for when to use it, what to use instead, or how it relates to the similarly named sibling relationship tool.

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