Skip to main content
Glama
G-Core
by G-Core

cloud_insts_ls

List cloud instances in a specified project and region, with filters for name, status, IP address, tags, and other criteria.

Instructions

List all instances in the specified project and region.

Results can be filtered by various parameters like name, status, and IP address.

Args: project_id: Project ID

region_id: Region ID

available_floating: Only show instances which are able to handle floating address

changes_before: Filters the instances by a date and time stamp when the instances last changed.

changes_since: Filters the instances by a date and time stamp when the instances last changed status.

exclude_flavor_prefix: Exclude instances with specified flavor prefix

exclude_secgroup: Exclude instances with specified security group name

flavor_id: Filter out instances by flavor_id. Flavor id must match exactly.

flavor_prefix: Filter out instances by flavor_prefix.

include_ai: Include GPU clusters' servers

include_baremetal: Include bare metal servers. Please, use GET /v1/bminstances/ instead

include_k8s: Include managed k8s worker nodes

ip: An IPv4 address to filter results by. Note: partial matches are allowed. For example, searching for 192.168.0.1 will return 192.168.0.1, 192.168.0.10, 192.168.0.110, and so on.

limit: Optional. Limit the number of returned items

name: Filter instances by name. You can provide a full or partial name, instances with matching names will be returned. For example, entering 'test' will return all instances that contain 'test' in their name.

offset: Optional. Offset value is used to exclude the first set of records from the result

only_isolated: Include only isolated instances

only_with_fixed_external_ip: Return bare metals only with external fixed IP addresses.

order_by: Order by field and direction.

profile_name: Filter result by ddos protection profile name. Effective only with with_ddos set to true.

protection_status: Filter result by DDoS protection_status. if parameter is provided. Effective only with with_ddos set to true. (Active, Queued or Error)

status: Filters instances by status.

tag_key_value: Optional. Filter by tag key-value pairs.

tag_value: Optional. Filter by tag values. ?tag_value=value1&tag_value=value2

type_ddos_profile: Return bare metals either only with advanced or only basic DDoS protection. Effective only with with_ddos set to true. (advanced or basic)

uuid: Filter the server list result by the UUID of the server. Allowed UUID part

with_ddos: Include DDoS profile information in the response when set to true. Otherwise, the ddos_profile field in the response is null by default.

with_interfaces_name: Include interface_name in the addresses

extra_headers: Send extra headers

extra_query: Add additional query parameters to the request

extra_body: Add additional JSON properties to the request

timeout: Override the client-level default timeout for this request, in seconds

Note: Pass the numeric project_id. When a project name is provided, resolve it via cloud.projects.list/cloud.projects.get. If nothing is specified, fetch the account's default project first and use that ID. Pass the numeric region_id. Resolve region names with cloud.regions.list or cloud.regions.get. If no region is mentioned, obtain the default region ID before calling this tool.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYes
region_idYes
available_floatingNo
changes_beforeNo
changes_sinceNo
exclude_flavor_prefixNo
exclude_secgroupNo
flavor_idNo
flavor_prefixNo
include_aiNo
include_baremetalNo
include_k8sNo
ipNo
limitNo
nameNo
offsetNo
only_isolatedNo
only_with_fixed_external_ipNo
order_byNo
profile_nameNo
protection_statusNo
statusNo
tag_key_valueNo
tag_valueNo
type_ddos_profileNo
uuidNo
with_ddosNo
with_interfaces_nameNo
extra_headersNo
extra_queryNo
extra_bodyNo
timeoutNo
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral transparency. It does not disclose that this is a read-only operation (safe side effect), nor does it mention authentication requirements, rate limits, or output behavior. For a list tool, this is a significant gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the main purpose but becomes lengthy due to the extensive parameter list and note. While the detail is necessary given 32 parameters, it could be more succinct by grouping related filters or using tables. The structure is logical but verbose.

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?

Given the tool's complexity (32 parameters, no output schema, no annotations), the description covers parameter semantics well and provides a helpful resolution note. However, it lacks information about output format, pagination (limit/offset behavior), error handling, and default values for optional parameters, leaving minor gaps.

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

Parameters5/5

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

Schema description coverage is 0%, so the description fully compensates with a detailed docstring for each parameter. It explains partial matching (ip, name), dependencies (profile_name etc. require with_ddos), and filtering nuances. This adds substantial meaning beyond the schema.

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 begins with a clear verb+resource statement: 'List all instances in the specified project and region.' It specifies scope and resource, and distinguishes from sibling tools like cloud_insts_get (single instance) and cloud_insts_act (actions). The extensive parameter list further clarifies the filtering capability.

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?

The description includes a note on resolving project_id and region_id, offering guidance on parameter preparation. However, it does not explicitly state when to use this tool versus alternatives (e.g., cloud_insts_get for a single instance) or when not to use it, missing clear usage boundaries.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/G-Core/gcore-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server