Skip to main content
Glama
erayendes

Heimdall App Store Connect MCP

by erayendes
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

app_encryption_declarations__get

Read-onlyIdempotent

Retrieve details for a specific app encryption declaration by ID, including optional related records like app, builds, or documents.

Instructions

Read one app encryption declaration by ID. [GET /v1/appEncryptionDeclarations/{id}]

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesID from the matching list call.
includeNocomma-separated list of relationships to include Pull related records in the same call. Without it, checking a relationship costs one extra call per row returned.
fields_appEncryptionDeclarationsNothe fields to include for returned resources of type appEncryptionDeclarations Return only these attributes. A full row set can exceed 200 KB.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.0.1
    • addedInput schema / properties / id / description
      Added value: +"ID from the matching list call."
  2. Changed3 schema fields changedv2.0.0
    • addedInput schema / properties / fields_appEncryptionDeclarations
      Added value: +{
+  "description": "the fields to include for returned resources of type appEncryptionDeclarations Return only these attributes. A full row set can exceed 200 KB.",
+  "items": {
+    "enum": [
+      "appDescription",
+      "createdDate",
+      "usesEncryption",
+      "exempt",
+      "containsProprietaryCryptography",
+      "containsThirdPartyCryptography",
+      "availableOnFrenchStore",
+      "platform",
+      "uploadedDate",
+      "documentUrl",
+      "documentName",
+      "documentType",
+      "appEncryptionDeclarationState",
+      "codeValue",
+      "app",
+      "builds",
+      "appEncryptionDeclarationDocument"
+    ],
+    "type": "string"
+  },
+  "type": "array"
+}
    • removedInput schema / properties / id / description
      Removed value: -"Resource identifier."
    • changedInput schema / properties / include / description
      Previous value: -"comma-separated list of relationships to include"New value: +"comma-separated list of relationships to include Pull related records in the same call. Without it, checking a relationship costs one extra call per row returned."
  3. First observedv1.3.0

TDQS

B3.3/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds the GET method but provides no additional behavioral context, such as the ability to include relationships or the potential for large responses. This is minimal added value beyond the annotations.

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

Conciseness5/5

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

The description is a single, efficient sentence that front-loads the action and resource. It avoids redundancy and contains no filler, earning full marks for conciseness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the simplicity of a get-by-ID tool and the presence of full schema coverage and safety annotations, the description is minimally viable but lacks guidance on optional relationship inclusion (include) and field selection (fields). It does not explain when to prefer this over sibling tools, making it adequate but not complete.

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?

The description does not mention parameters, but schema description coverage is 100%, with each parameter (id, include, fields_appEncryptionDeclarations) documented in the input schema. The optional include and fields parameters already have meaningful descriptions in 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.

Purpose5/5

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

The description states a specific action ('Read') and resource ('app encryption declaration') with an ID parameter, clearly distinguishing it from list operations. Including the exact endpoint [GET /v1/appEncryptionDeclarations/{id}] reinforces the resource and method.

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 is provided on when to use this tool versus alternatives such as app_encryption_declarations__list or the related document getter. The context signals show sibling tools but the description does not mention them or any selection criteria.

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