Skip to main content
Glama

update_service

Modify a hosted service's name, size, database, port, start command, or public HTTPS access; changes restart the service.

Instructions

Servis ayarlarını değiştirir (ad, boyut, veritabanı, port, başlatma komutu, dışarıdan HTTPS erişimi). Değişiklik servisi yeniden 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": "update_service"
  }
}

Input Schema

NameRequiredDescriptionDefault
dbNo
nameNo
portNo
sizeNo
startCmdNo
serviceIdYesServis id (list_services / create_service yanıtındaki id)
publicHttpNo

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 behavioral burden. It usefully discloses one key side effect — that the change restarts the service — but says nothing about required permissions, whether unspecified fields are left untouched (partial update), whether behavior differs per field, or what happens on failure.

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?

Two tight sentences with the side effect front-loaded in the second position. Nothing is wasted, though the parenthetical field list is dense and could read as boilerplate.

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 7-parameter mutation tool with no annotations and no output schema, the definition covers purpose and the restart side effect but leaves partial-update semantics, serviceId meaning, allowed enum values, and result behavior unstated. It is minimally workable but thinner than the tool's risk profile warrants.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 14%, so the description needs to compensate. It names six of the seven parameters but adds no meaning beyond label-level: no valid values for the db/size enums, no port range, no note that all fields other than serviceId are optional, and serviceId is omitted entirely.

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?

Names a specific verb ('değiştirir' / modifies) and resource (service settings) and enumerates the mutable fields (name, size, database, port, start command, public HTTPS access). This distinguishes it from create_service/delete_service, though the serviceId parameter is not mentioned.

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 field list implicitly tells the agent this is the tool for altering existing service configuration rather than creating, deleting, or restarting, but there is no explicit when-to-use guidance or routing to siblings such as deploy_service, set_service_env, or restart_service. No prerequisites or exclusions are stated.

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