Skip to main content
Glama

get_service

Retrieve a hosted bot service's status, status description, latest release, start command, environment variable names, and resource usage by service ID.

Instructions

Bir servisin ayrıntısı: durum, durum açıklaması, son sürüm, başlatma komutu, env değişken ADLARI (değerler gösterilmez), kaynak kullanımı.

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

A3.6/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden, and it does disclose a genuinely non-obvious behavioral trait: env variables are returned as NAMES only, values are not shown. That prevents an agent from expecting secrets and is exactly the kind of context annotations would otherwise supply. It still omits the read-only nature explicitly and behavior on an unknown/invalid serviceId.

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 that front-loads the resource and then lists the returned fields with zero filler. Every clause earns its place, including the parenthetical about redacted env values.

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?

No output schema exists, so the description must convey the return shape, and it enumerates the key fields well enough for an agent to decide whether to call it. Remaining gaps are minor for a one-param read tool: no explicit statement that it is read-only and no error/not-found behavior. Note the description is in Turkish while tool and parameter names are English, a small consistency cost for non-Turkish agents.

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 a single required parameter and schema description coverage is 100% (format uuid, described as the id from list_services/create_service). The description adds no syntax, format, or sourcing detail beyond the schema, so the baseline 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?

The description names a concrete resource (a service) and enumerates exactly what the response contains: status, status description, last release, start command, env variable names, and resource usage. An agent can tell this apart from get_service_logs or list_services by the field list. It lacks an explicit verb ('get/details') and does not name a sibling it is not, so it stops short of 5.

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 when-to-use or when-not-to-use guidance: nothing says to prefer this over list_services for a single lookup or over get_service_logs for diagnostics. The only routing hint (serviceId comes from list_services/create_service responses) lives in the schema, not the description.

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