Skip to main content
Glama

WhatsDownNow

Check a dependency stack

check_stack
Read-onlyIdempotent

Readiness check for a set of dependencies (e.g. an AI app's stack: chatgpt, claude, aws, vercel, supabase, stripe). Returns overall verdict (worst of the set), ready=true only if all are up, and per-service status. Use before running jobs that depend on these services.

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": {
      "slugs": "<slugs>"
    },
    "name": "check_stack"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and non-destructive, so the safety profile is covered. The description adds real behavioral content beyond that: the verdict is the worst of the set, ready=true only when every service is up, and per-service status is returned. It omits edge behavior for unknown or ambiguous slugs, keeping it from a 5.

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?

Three tight sentences: purpose first, return semantics second, usage guidance last. No redundant restatement of the title and no filler.

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

Completeness4/5

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

There is no output schema, and the description compensates by describing the return shape (overall verdict, ready flag, per-service status). For a single-parameter read-only probe this is nearly sufficient; only edge-case handling of invalid slugs is unaddressed.

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 0%, so the description must carry the load, and it does give example slug values (chatgpt, claude, aws, vercel, supabase, stripe) that clarify these are service identifiers rather than arbitrary strings. It does not explain the 1–90 cardinality or exact slug format, leaving a small gap.

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

Purpose4/5

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

States a specific verb and resource: a readiness check over a set of dependency slugs, with concrete examples of what a 'stack' means. It is clearly distinguishable from the alert-stack CRUD siblings by being a health/readiness probe. It does not explicitly name a sibling it competes with, so it falls just short of a 5.

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

Usage Guidelines4/5

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

Explicitly says when to call it: 'Use before running jobs that depend on these services,' which tells the agent the pre-flight gate pattern. There are no stated exclusions or alternatives, but the invocation context is unambiguous.

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.