Skip to main content
Glama

hosts_list

Read-onlyIdempotent

List the servers reachable through Termalin (your tunnel agents). Returns id, name, whether the server is online, the user commands run as, when it was last seen, its country, ip (the public address the server's Connector connects from; null until it has connected), and ownerNote — what the owner wrote about that server for you (what it is, what to leave alone); follow it. 'policy' says what you may do there: full, allowlist (only listed commands; allowedCommands holds the server's list, no file writes) or readonly (no commands, no file writes). 'tags' are the owner's labels for the server (prod, neuroshop…) and 'groups' the ones Termalin knows by itself (os:linux, distro:ubuntu, release:ubuntu-24.04, country:fr); pass 'tag' to list only the servers that have all of the given ones. Use the id (or the exact name) as 'host' in the other tools.

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

Input Schema

NameRequiredDescriptionDefault
tagNoOnly servers with every one of these tags or groups, e.g. "prod" or ["release:ubuntu-24.04", "prod"]

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / tag
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    }
      +  ],
      +  "description": "Only servers with every one of these tags or groups, e.g. \"prod\" or [\"release:ubuntu-24.04\", \"prod\"]"
      +}
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

The annotations already establish a read-only, idempotent, non-destructive, open-world listing operation. The description adds substantial context beyond that: the returned fields, how 'policy' constrains allowed actions (full, allowlist, readonly), what 'ownerNote' means and that it should be followed, and the fact that ip is null until the server connects.

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?

The description is long and written as a dense paragraph, but it is front-loaded with the core purpose and most sentences carry necessary information about return fields, policy, tags, groups, and host usage. It could be structured more readably, but it contains little obvious filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description carries the full burden of explaining return values, and it does so thoroughly: id, name, online status, command user, last seen, country, ip, ownerNote, policy, tags, and groups. It also explains how to filter and how to use the id in other tools, leaving little essential information missing for a discovery tool.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds useful meaning by distinguishing 'tags' (owner-defined labels such as prod) from 'groups' (Termalin-known values such as os:linux or country:fr). It also clarifies that the filter requires all supplied tags, which slightly extends the schema's 'every one of these tags or groups' wording.

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?

The description starts with a specific verb and resource: 'List the servers reachable through Termalin (your tunnel agents).' It clearly establishes that this is the server-inventory tool and distinguishes it from action-oriented siblings by explaining that returned ids are used as 'host' in the other tools.

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?

It gives clear operational guidance: use the returned id or exact name as 'host' in other tools, and pass 'tag' to restrict the listing to servers matching all supplied tags or groups. It does not explicitly compare against sibling alternatives such as server_metrics or ssh_exec, but the intended use case is very clear.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.