Skip to main content
Glama

stop_service

Stops a running hosted bot service by service ID while preserving its data. Use it to halt a service without deleting stored information.

Instructions

Servisi durdurur (veriler korunur).

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>"
    },
    "name": "stop_service"
  }
}

Input Schema

NameRequiredDescriptionDefault
serviceIdYesServis id (list_services / create_service yanıtındaki id)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It does disclose one valuable trait — that data survives the operation — but says nothing about reversibility (can start_service bring it back?), whether in-flight requests are drained, whether the stop is synchronous, or what permissions are required for this mutation.

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?

A single short sentence with the key side-effect note front-loaded; nothing is wasted. It is arguably over-terse for a mutation tool, but no sentence is redundant.

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?

For a mutation tool with no annotations and no output schema, the definition covers purpose and data preservation but omits reversibility, async/sync behavior, and the resulting service state. Adequate to identify the tool, thin on what an agent needs to call it confidently.

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 description coverage is 100% and the single parameter is fully documented in the schema itself, including where to obtain the serviceId, so the baseline applies. The description adds no parameter detail, but there is nothing left to clarify for a one-parameter tool.

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?

"Servisi durdurur" states a specific verb (stop) and resource (service), which is unambiguous against siblings such as start_service or delete_service. The parenthetical "veriler korunur" further separates it from delete_service, though no sibling is named explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: the note that data is preserved hints at the stop-vs-delete distinction, but the description never states when to choose this over restart_service, delete_service, or start_service, nor any prerequisites.

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