Skip to main content
Glama

Check a stack

check_stack
Read-onlyIdempotent

Check a stack of two to ten tools against every CDP in CdpHub's directory, as the stack check on cdphub.com does: how many CDPs list all of them and which, those CDPs grouped by how they connect to each tool with each group counted, how they connect to each tool on its own with each group counted and a sentence for it, the CDPs that miss exactly one tool grouped by the tool they miss, and a link to the same check on cdphub.com. Use it for any question about two or more tools together, such as which CDPs fit a company's stack.

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

Input Schema

NameRequiredDescriptionDefault
toolsYesThe tools, for example ["Shopify", "Klaviyo", "Snowflake"]: two to ten.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and closed-world, so safety is covered. What the description adds is the shape of the response: coverage counts, groups by connection, per-tool breakdowns, near-miss CDPs, and a link back to cdphub.com. That is useful, but it is return-value content rather than behavioral traits such as error handling for unrecognized tool names or latency limits.

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 opening clause is well front-loaded, but the middle is one enormous run-on enumeration of five result components that is hard to parse in a single pass. The usage guidance arrives last, when it would be more effective near the front. Nothing is outright wasted, yet the structure could be tightened considerably.

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?

With no output schema, the description carries the full burden of explaining what comes back, and it does so in detail across all five result sections. The main gap is failure behavior when a supplied tool name is not in the directory, which an agent preparing a call would want to know.

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 coverage is 100% and the single parameter already carries its own example and the 2-to-10 bound, so the schema does the work. The description restates 'two to ten tools' but adds no new meaning about accepted name formats, fuzzy matching, or whether unknown tool strings error out. Baseline 3 applies.

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?

Opens with a specific verb and resource: check a stack of two to ten tools against every CDP in the directory. That is concrete enough to separate it from get_tool or get_cdp, and the closing line ('two or more tools together') reinforces the batch scope. It never names compare_cdps explicitly, so the boundary with that sibling is left to inference.

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?

Gives a clear triggering condition: any question involving two or more tools together, with a company-stack example. There is no explicit when-not clause and no named alternative for the single-CDP or single-tool case, which keeps it short of a 5.

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