Skip to main content
Glama

start_service

Starts a stopped hosted trading bot service using its service ID, so the service can resume running.

Instructions

Durmuş servisi başlatır.

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

B3/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden. It never states whether the call is synchronous, what state the service ends in, what happens if the service is already running, or whether the operation is idempotent — important for a state-mutating lifecycle action.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single front-loaded sentence with zero padding, which is structurally clean. However, the brevity comes at the cost of nearly all operational detail, so it reads as under-specification rather than disciplined conciseness.

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 mutation on a service's lifecycle with no annotations and no output schema, meaning the description is the only channel for behavioral context. It supplies none of it — no success/failure conditions, no post-call state, no mention of what is affected on the running workload.

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?

There is only one parameter and schema description coverage is 100%; the schema already explains serviceId as a UUID taken from list_services/create_service responses. The description adds no additional meaning beyond the schema, which is the expected baseline at full coverage.

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?

The description gives a concrete verb and resource ('starts the service') plus a precondition ('stopped'), so an agent knows the operation targets a halted service. It does not explicitly distinguish this from restart_service or deploy_service, so sibling differentiation is left to inference.

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?

The qualifier 'stopped' implies when the tool applies (the service is currently halted), which is usable guidance. There is no explicit when-not condition and no named alternative for restarting an already-running service, so the guidance remains implied rather than stated.

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