Skip to main content
Glama

rollback_service

Reverts a hosted service to its previous successful release or a specified release ID, restoring a stable version after a faulty deployment.

Instructions

Bir önceki başarılı sürüme (ya da verilen releaseId'ye) geri döner.

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": "rollback_service"
  }
}

Input Schema

NameRequiredDescriptionDefault
releaseIdNo
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.4/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 entire burden for what is effectively a mutation. It discloses one useful behavioral fact (the default fallback to the previous successful release), but says nothing about side effects such as service restart or downtime, whether the rollback is itself reversible, required permissions, or whether a new release record is created.

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?

A single sentence with zero filler, and the default behavior is front-loaded ahead of the override case. Nothing is redundant or padded.

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?

Placeholder.

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 coverage is 50%: serviceId is documented in the schema, while releaseId is only typed as a uuid. The description compensates partially by establishing an either/or relationship — omit releaseId and the tool targets the previous successful release, supply it and the tool targets that release — which the schema alone does not express. It still adds no format or sourcing detail for releaseId.

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 names a specific verb (roll back) and resource (service/release) and states the default target ('the previous successful release'), which lets an agent separate it from deploy_service or list_releases. It stops short of explicitly naming any sibling, so it is clear but not fully differentiated.

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: an agent can infer this is the 'undo a bad deploy' path, and the description implies releaseId overrides the default. There is no explicit when-not guidance, no pointer to list_releases for discovering a releaseId, and no mention of preconditions such as a prior successful release existing.

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