Skip to main content
Glama
Sign In

Meridian

by ai.the-meridian
OverviewDiscussions(2)Admin

Get Shopify Alert

shopify_alert_get
Read-only

Returns a single Shopify API-deprecation alert's detail: the same fields as shopify_alerts_list, plus the existing stored AI fix suggestion (fix_suggestion (summary, steps, references, grounded) or null when none has been generated yet; fix_suggested_at; fix_error/fix_failed_at when generation failed). Never generates a new fix suggestion. Takes the app_id returned by apps_list and the alert_id returned by shopify_alerts_list. Works for acknowledged alerts too, unlike shopify_alerts_list, which only lists open ones. Requires the shopify_alerts.view permission on the 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": {
      "app_id": "<app_id>",
      "alert_id": "<alert_id>"
    },
    "name": "shopify_alert_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
app_idYesThe app uuid returned by `apps_list`.
alert_idYesThe alert uuid returned by `shopify_alerts_list`.
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. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the readOnly/openWorld annotations, it discloses the auth requirement (`shopify_alerts.view`), the side-effect boundary (never generates a fix), and the exact return shape including `fix_suggestion` being null when absent and `fix_error`/`fix_failed_at` on failure. That is substantive context the annotations do not carry.

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?

Front-loaded with the core purpose and ID sourcing, then behavior. The nested parenthetical enumerating `fix_suggestion` sub-fields is dense and slows reading, but each clause still carries information an agent needs.

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?

With no output schema, the description compensates by describing the returned fields and their null/error variants. For a three-parameter, non-destructive single-record read, nothing needed to invoke or interpret the call is missing.

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 all three parameters, including where `app_id` and `alert_id` originate. The description restates the same provenance for the two required IDs but says nothing about `organization_id` slug resolution, so it adds no meaning beyond the schema.

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 opens with a specific verb and resource: 'Returns a single Shopify API-deprecation alert's detail', and immediately anchors it against the sibling by noting it exposes 'the same fields as `shopify_alerts_list`'. An agent can distinguish this single-item read from the list tool without opening either 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?

It gives explicit routing conditions: use this when the alert may be acknowledged, since `shopify_alerts_list` 'only lists open ones'. It also names where the two required IDs come from (`apps_list`, `shopify_alerts_list`) and rules out a nearby expectation with 'Never generates a new fix suggestion'.

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

All Meridian toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources