Skip to main content
Glama

List the hosts of a private fleet

edgegap_list_fleet_hosts
Read-only

List hosts in a private fleet with status, IP, and location; identify ACTIVE host_id values to pass for private deployments.

Instructions

List the hosts in one of the organization's private fleets (dedicated machines Edgegap manages for you), with status, IP and location. Only ACTIVE hosts accept deployments. Pass their host_id values to edgegap_deploy as private_host_ids to place a server on them first. Each host includes 6 TB of free egress per month; deployments that overflow to the cloud pay cloud egress ($0.10 per GB). Organizations without private fleets get an error from the API.

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": {
      "fleet_name": "<fleet_name>"
    },
    "name": "edgegap_list_fleet_hosts"
  }
}

Input Schema

NameRequiredDescriptionDefault
fleet_nameYesThe private fleet name, as shown in the dashboard.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.15.1

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already establish readOnlyHint=true, but the description adds real behavioral context beyond them: an active-status filter that gates deployability, a defined free egress quota (6 TB/month) with overflow pricing ($0.10/GB), and the failure mode for orgs lacking a private fleet. These are exactly the operational details an agent needs to interpret results and decide follow-up actions.

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?

Four sentences, front-loaded with purpose and then chaining instructions, with no filler. The egress quota and cloud-overflow pricing are slightly tangential to listing hosts, but they do inform whether an agent should keep a deployment on private hosts.

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?

No output schema exists, and the description compensates by naming the returned attributes (status, IP, location, host_id) and the key semantic distinction among them (ACTIVE vs not). Combined with the chaining guidance to edgegap_deploy, an agent has everything needed to call and act on results.

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?

Only one parameter exists and schema coverage is 100%, with the schema itself explaining that fleet_name is the dashboard-visible name. The description implies the fleet belongs to the organization but adds no format, casing, or lookup guidance beyond the schema. 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 specific verb (list) and resource (hosts in a private fleet), and defines the resource inline ("dedicated machines Edgegap manages for you") along with the fields returned: status, IP and location. An agent can distinguish this from neighboring list/get tools without opening the schema.

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 concrete usage context: only ACTIVE hosts accept deployments, and the returned host_id values feed edgegap_deploy as private_host_ids. It also warns that organizations without private fleets get an API error. It does not explicitly contrast with edgegap_fleet_health, which is the closest conceptual sibling, so it stops short of full when-not guidance.

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