Skip to main content
Glama

deploy_service

Uploads a local folder or compiled Linux x86_64 program to a hosted service, waits for the build, and returns the build result and logs for deployment troubleshooting.

Instructions

Yerel bir klasörü (ya da tek bir derlenmiş Linux x86_64 programını) zipleyip servise yükler, derlemeyi bekler ve sonucu + derleme logunu döner. .gitignore'a uyar; node_modules, .venv, .git, .env* gönderilmez (bağımlılıklar sunucuda requirements.txt / package.json'dan kurulur). Derleme hata verirse logu oku, kodu düzelt ve tekrar deploy_service çağır. Başarılıysa get_service_logs ile çalışma çıktısını izle.

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

Input Schema

NameRequiredDescriptionDefault
pathYesYüklenecek klasörün (ya da tek program dosyasının) mutlak yolu
waitNoDerleme bitene kadar bekle (varsayılan true, en fazla ~3 dk)
serviceIdYesServis id (list_services / create_service yanıtındaki id)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

A4.2/5.0
Behavior4/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 and does substantial work: it discloses that .gitignore is honored, that node_modules, .venv, .git, and .env* are excluded, that dependencies are installed server-side from requirements.txt/package.json, and that a build log is returned. It omits whether an existing running deployment is overwritten or restarted, and whether the operation is reversible via rollback_service.

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?

Four dense sentences with no filler, front-loaded with what the tool does, followed by upload filtering rules and the failure/success workflow. Every sentence contributes actionable information for the agent.

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?

With no output schema and no annotations, the description explains the return (result plus build log) and the retry loop, which is sufficient to invoke and react to the tool. It stops short of covering deployment side effects such as whether the running service is replaced or whether authorization is required.

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%, so all three parameters (serviceId, path, wait) are already documented in the schema, including path accepting a folder or single program file and wait's default and roughly 3-minute cap. The description restates the folder-or-binary and build-wait behavior rather than adding new meaning, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a concrete verb chain (zip local folder or single Linux x86_64 binary, upload to the service, wait for the build, return result plus build log). This clearly distinguishes it from sibling tools like create_service, update_service, and get_service_logs, which are administrative or read-only rather than deploy/build operations.

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

Usage Guidelines4/5

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

Gives explicit follow-up routing: on build failure, read the log, fix the code, and call deploy_service again; on success, monitor runtime output with get_service_logs. It does not state when to prefer this over create_service or update_service, so a sibling-selection boundary is left implicit.

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