Skip to main content
Glama

Demo stop

demo_stop
Destructive

Tear down a PR demo deployed by deploy_pr_demo: deletes its ankra-demo-pr- namespace on the staging cluster and marks the tracking record destroyed. Provide either the namespace or the pr_number.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "demo_stop"
  }
}

Input Schema

NameRequiredDescriptionDefault
namespaceNoThe demo namespace (ankra-demo-pr-<n>). Optional if pr_number is given.
pr_numberNoThe pull-request number whose demo to stop. Optional if namespace is given.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

The annotations already declare destructiveHint=true and readOnlyHint=false, and the description usefully adds exactly what is destroyed: the ankra-demo-pr-<n> namespace on staging and the tracking record. It does not discuss permissions, confirmation requirements, or failure behavior, but it adds meaningful context beyond the annotations without contradicting them.

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 concise and front-loaded with the core action. Every sentence adds useful information: the linked deployment tool, the affected namespace, the side effect on the tracking record, and the input choice.

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?

For a two-parameter destructive tool with full schema coverage and annotations carrying the safety profile, the description covers the essential behavior and target. It would be stronger with a note about irreversibility, confirmation, or what happens if the demo does not exist, but those are secondary gaps.

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%, so the input schema already documents both namespace and pr_number, including that each is optional when the other is provided. The description reinforces the either/or requirement but adds no syntax or semantic detail 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 uses a specific verb and resource: tearing down a PR demo deployed by deploy_pr_demo. It also identifies the concrete namespace pattern and staging cluster, which distinguishes it from siblings like deploy_pr_demo, redeploy_demo, and inspect_demo.

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?

The description makes the use case clear: stop a PR demo that was created by deploy_pr_demo. It does not explicitly name when not to use it or contrast it with other demo-related tools such as inspect_demo or redeploy_demo, so it lacks full alternative routing.

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.