Skip to main content
Glama

teardown_service

Destructive

Removes a service's proxy host for a domain and, optionally, its DNS record. Shows the exact teardown plan before applying changes.

Instructions

Reverse expose_service: delete the proxy host for domain (found by name unless proxy_host_id is given) and, if dns_record_id is given, that DNS record. The exact plan is shown to the person first.

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": {
      "domain": "<domain>"
    },
    "name": "teardown_service"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYes
dry_runNo
dns_zone_idNo
dns_record_idNo
proxy_host_idNo

Output Schema

NameRequiredDescriptionDefault
noteNo
errorsNo
dry_runNo
plannedNo
successNo
approved_byNo
steps_completedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already flag destructive=true and openWorld=true, so the description's added value is the explicit blast radius (proxy host plus optional DNS record) and the order in which they are removed, plus the note that a plan is presented to the person first. It leaves dry_run unexplained, which matters for a destructive tool with 0% schema coverage.

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?

Two sentences, no filler, and the destructive action is front-loaded ahead of the conditional clauses. Every clause carries information the agent needs.

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

Completeness3/5

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

Output schema exists so return values need no explanation, but for a destructive 5-parameter tool the description should still explain what dry_run does and what dns_zone_id is for. The core destructive semantics are covered; the preview/scope controls are not.

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?

With 0% schema description coverage the description must compensate, and it does cover three of five parameters: domain lookup by name, proxy_host_id as an override, and dns_record_id as the opt-in for DNS deletion. dry_run and dns_zone_id are never mentioned, so the compensating work is only partial.

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 and resources (delete the proxy host and, optionally, the DNS record) and anchors itself to a named sibling by declaring it the reverse of expose_service. An agent can distinguish it from every other sibling without opening the schema.

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?

"Reverse expose_service" gives a clear selection rule against that specific sibling, and the conditional phrasing tells the agent when the DNS record is also removed. It does not say when NOT to use it (e.g., when only the DNS record should be removed, or when the host was created outside expose_service).

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