Skip to main content
Glama

list_services

List etrink-hosted Python, Node.js, and Linux services with status, size, address, resource usage, and quota to monitor deployments.

Instructions

etrink'te barındırılan servislerini listeler (Python / Node.js / hazır Linux programı): durum, boyut, adres, kaynak kullanımı, kota. Durumlar: no_release (kod yok), building, starting, running, crashed, stopped, error.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_services"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

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?

With no annotations, the description carries the disclosure burden and does well: it enumerates the fields returned (status, size, address, resource usage, quota) and decodes every status value including the non-obvious no_release. It does not state auth requirements, pagination, or ordering, which keeps it short of a 5.

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?

Two compact sentences: the first front-loads scope and returned fields, the second handles status semantics. No filler, and the enumeration format makes the status list scannable.

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?

There is no output schema, and the description compensates by describing the response shape and status vocabulary, which is the main thing an agent needs. Gaps remain around pagination, ordering, and permissions for a tool that could return many services.

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

Parameters4/5

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

The tool takes no parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. The field/status listing it does provide is return-value context rather than parameter guidance.

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 specific verb and resource ('lists services hosted on etrink') plus the supported service kinds (Python / Node.js / ready-made Linux program). This is enough for an agent to distinguish it from get_service (single service) and list_releases without opening any schema.

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: a zero-argument enumeration tool whose purpose makes it the obvious first call before get_service or service actions. The description never says when to prefer it over list_releases or when a targeted get_service call would be better, so there is no explicit routing guidance.

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