Skip to main content
Glama

restart_service

Restart a hosted bot service using its service ID, including crashed instances, to restore operation.

Instructions

Servisi yeniden başlatır (çöktüyse de).

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": "restart_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

C2.9/5.0
Behavior2/5

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

With no annotations supplied, the description carries the full burden. It discloses only that the restart succeeds even if the service has crashed; it says nothing about expected downtime, whether in-flight requests are killed, whether data/state is preserved, whether permissions are required, or what happens on a healthy running service.

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, front-loaded with the verb and resource, with zero filler. It is terse almost to a fault, but nothing in it is wasted.

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

Completeness2/5

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

This is a state-mutating operational tool with no annotations and no output schema, and the description covers only one edge case (crashed service). For an agent deciding between restart_service, start_service, stop_service, and rollback_service, key information about impact and side effects is missing.

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 description coverage is 100% and the single serviceId parameter is fully documented in the schema, including the uuid format and where to obtain the id. The description adds no further meaning about the parameter, so the baseline of 3 applies.

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?

States a specific verb and resource ('Servisi yeniden başlatır') and adds the qualifier '(çöktüyse de)' meaning it also works on a crashed service, which hints at how it differs from a plain start. It doesn't name start_service or stop_service among the siblings, so differentiation is only partial.

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

Usage Guidelines2/5

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

There is no explicit guidance on when to choose this over start_service, stop_service, or rollback_service; the parenthetical hints that it covers crashed services but leaves the agent to infer the rest. No prerequisites, no exclusions, no alternatives named.

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