Skip to main content
Glama

delete_service

Deletes a hosted bot service and schedules its data and database for permanent removal after 7 days; requires the service ID and slug confirmation. Use only when explicitly requested.

Instructions

Servisi siler. Geri alınamaz: /data ve veritabanı 7 gün sonra kalıcı silinir. confirm alanına servisin slug'ını aynen yaz. Kullanıcı açıkça istemedikçe çağırma.

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": {
      "serviceId": "<serviceId>",
      "confirm": "<confirm>"
    },
    "name": "delete_service"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmYesServisin slug'ı (onay)
serviceIdYesServis id (list_services / create_service yanıtındaki id)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations provided, the description carries the full behavioral burden and does well: it discloses irreversibility, the specific data affected (/data and the database), and a 7-day window before permanent deletion, which implies a grace period. It does not mention permission requirements or what happens to dependent resources like releases or deployments.

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?

Four short sentences, each earning its place: action, consequence, required confirmation input, and usage guardrail, ordered with the destructive warning front-loaded right after the verb. No filler or repetition.

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 no output schema, the definition covers what matters most: what gets destroyed, the retention window, and the confirmation contract. Missing only secondary context such as auth requirements or downstream effects on related resources.

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 already 100%, so baseline is 3, but the description adds real meaning: confirm must contain the service slug written exactly as-is, clarifying this is a typed-confirmation safety gate rather than an arbitrary string. It says nothing extra about serviceId beyond the schema's own note, which is acceptable given the schema's clarity.

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?

"Servisi siler" states a specific verb (delete) and resource (service) in the first clause, and the surrounding detail makes it unmistakable from siblings like stop_service or update_service. An agent can identify this as the destructive removal operation 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?

The final sentence gives an explicit exclusion: do not call unless the user explicitly requests it, which is exactly the right guardrail for a destructive tool. It stops short of naming alternatives (stop_service, rollback_service) that a cautious agent might prefer, so it is clear but not fully routing.

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