Skip to main content
Glama
Sign In

Edgegap

by dev.edgegap
OverviewDiscussionsAdmin
This connector has been deprecated

older mcp we are replacing it with another one.

Stop a deployment

edgegap_stop_deployment
DestructiveIdempotent

Gracefully stop one deployment by request_id, sending SIGTERM to the container. Stop every deployment you started for testing before ending your task. This tool stops exactly one deployment, named by its exact request_id: empty IDs, wildcards and lists are refused, and bulk stop is deliberately not exposed.

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": {
      "request_id": "<request_id>"
    },
    "name": "edgegap_stop_deployment"
  }
}

Input Schema

NameRequiredDescriptionDefault
dry_runNoShow the exact request (method, host, path, body) with secrets masked, and send nothing. Local checks still run. Use it to confirm a billable or destructive call before making it.
request_idYesThe exact request_id of the one deployment to stop, e.g. "61b1be8f54d9".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / dry_run
      Added value: +{
+  "description": "Show the exact request (method, host, path, body) with secrets masked, and send nothing. Local checks still run. Use it to confirm a billable or destructive call before making it.",
+  "type": "boolean"
+}
    • changedInput schema / properties / request_id / description
      Previous value: -"The request_id of the deployment to stop."New value: +"The exact request_id of the one deployment to stop, e.g. \"61b1be8f54d9\"."
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare destructive, idempotent, and open-world characteristics. The description adds real value beyond them: the SIGTERM termination mechanism, the strict single-deployment constraint, and the refusal of empty IDs/wildcards/lists, which tells the agent how invalid input behaves.

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?

Three tight sentences, front-loaded with the action and mechanism, then the workflow rule, then the constraint. No filler; the only minor redundancy is restating the single-deployment limit across two sentences.

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 destructive, no-output-schema tool, the description covers action, mechanism, scope, validation, and workflow. The one gap is whether the call is synchronous or whether termination must be confirmed via edgegap_wait_for_deployment, but that is a minor omission against otherwise thorough coverage.

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, but the description adds validation semantics the schema does not: empty IDs, wildcards, and lists are refused, reinforcing that exactly one literal request_id is expected. It also corroborates the dry_run intent documented in 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?

States a specific verb (stop), resource (deployment), and exact scope (one, by request_id), plus the mechanism (SIGTERM). An agent can immediately distinguish this from edgegap_deploy, edgegap_list_deployments, or edgegap_wait_for_deployment.

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 an explicit workflow instruction ('stop every deployment you started for testing before ending your task') and rules out bulk usage ('bulk stop is deliberately not exposed'). It does not name a sibling alternative, but since no bulk-stop sibling exists, the exclusion is effectively complete guidance.

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

All Edgegap toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources