Skip to main content
Glama

Check App Readiness

app_readiness_get
Read-onlyIdempotent

Checks whether an app is ready to deploy and run, in one call: the Shopify client ID and secret (SHOPIFY_API_KEY / SHOPIFY_API_SECRET), the Shopify Partner connection, the GitHub repository and its Dockerfile, whether pushes auto-deploy to production from a branch GitHub or GitLab reports as unprotected (a warning, code auto_deploy_production_branch_unprotected), Plan Builder plans, whether Plan Builder billing has the client ID and secret it reads (only the ones saved under Meridian SDK, never a SHOPIFY_API_KEY or SHOPIFY_API_SECRET variable), and for the environment: its managed database, Prisma session storage, Prisma migrations without a release command, the variables a Shopify app reads at boot, SCOPES against the access scopes of the repository's shopify.app.toml at the commit, and its custom domains.

Returns ready (false when any check fails), a summary count, and checks: each with key, status (pass, warn, fail), code (the problem, such as missing_shopify_client_secret; null on a pass), message, and fix (location in the Meridian dashboard and its url). A fail is what makes a deploy fail in seconds, before its build; a warn deploys but the app is likely to misbehave. The one fail a deploy does not stop on is shopify_billing: merchants cannot subscribe, but the app boots, so the deploy logs it as a warning.

Run it before deployment_create, and after a deployment failed with error_code invalid_config. Takes the app_id from apps_list and an optional environment_id from environments_list (default: the production environment; an app with no environment yet gets the app-level checks only). Values are never returned.

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": {
      "app_id": "<app_id>"
    },
    "name": "app_readiness_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
app_idYesThe app this call works on: its `app_id` uuid from `apps_list`.
environment_idNoThe environment to check, from `environments_list`. Defaults to the production environment.
organization_idNoAn organisation uuid or slug. When supplied, `app_id` is resolved within that organisation and may be a slug instead of a uuid, mirroring the Meridian web app.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / app_id / description
      Previous value: -"The app uuid returned by `apps_list`."New value: +"The app this call works on: its `app_id` uuid from `apps_list`."
  2. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds substantive context beyond them: `fail` blocks a deploy in seconds before build, `warn` deploys but risks misbehavior, and the single exception where `shopify_billing` fails without stopping the deploy. It also discloses that secret values are never returned and that an app with no environment gets app-level checks only.

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

Conciseness4/5

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

Purpose and invocation guidance are front-loaded, and every paragraph carries functional information. It is dense, however, with deeply nested parentheses around the billing and SCOPES caveats, which slows parsing of an otherwise well-organized definition.

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

Completeness5/5

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

For a read-only diagnostic tool with no output schema, the description supplies the full return shape (`ready`, `summary`, `checks` with `key`/`status`/`code`/`message`/`fix`), status semantics, and example codes — nothing an agent needs to call or interpret it is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3; the description still adds the default-environment behavior and the no-environment edge case ('app-level checks only'), which the schema does not state. It does not expand on `organization_id` slug resolution beyond what the schema already says.

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?

States a specific verb and resource ('Checks whether an app is ready to deploy and run') and then enumerates exactly what is checked — credentials, Partner connection, repository/Dockerfile, auto-deploy branch protection, Plan Builder, database/Prisma, boot variables, SCOPES vs shopify.app.toml, custom domains. An agent can distinguish this from app_get or deployment_get without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Gives explicit invocation points: run before `deployment_create`, and after a deployment failed with `error_code` `invalid_config`. It also names the source tools for its inputs (`apps_list` for app_id, `environments_list` for environment_id) and states the default environment.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources