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

cloud_insts_imgs_ls

Retrieve available images in a project and region, filterable by visibility, tags, and pricing.

Instructions

Retrieve a list of available images in the project and region.

The list can be filtered by visibility, tags, and other parameters. Returned entities are owned by the project or are public/shared with the client.

Args: include_prices: Show price

private: Any value to show private images

tag_key: Filter by tag keys.

tag_key_value: Filter by tag key-value pairs. Must be a valid JSON string.

visibility: Image visibility. Globally visible images are public

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
include_pricesNo
privateNo
tag_keyNo
tag_key_valueNo
visibilityNo
extra_headersNo
extra_queryNo
extra_bodyNo
timeoutNo
Behavior4/5

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

No annotations provided; the description implies a read-only operation through 'Retrieve list' and lacks side-effect language. While not explicitly stating idempotency, the intent is clear and truthful.

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?

Well-organized with initial purpose, filtering capabilities, ownership note, then Args list, and Note section. A few generic parameters (extra_headers) add length but structure aids readability.

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?

Covers all parameters and essential resolution logic. Lacks explicit return format description, but given no output schema, the mention of 'returned entities' provides enough context for an image list.

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%, but the description compensates with an Args section explaining every parameter's purpose (e.g., 'include_prices: Show price', 'visibility: Image visibility'). The Note also clarifies project_id and region_id resolution.

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?

Explicitly states 'Retrieve a list of available images' with verb+resource. Differentiates from sibling tools like cloud_insts_imgs_del (delete), cloud_insts_imgs_get (get single), and cloud_insts_imgs_new_vol (create) by focusing on listing.

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?

Provides clear context on when to use by detailing how to resolve project_id and region_id, including fallback to default. Does not explicitly exclude alternative list tools, but the note on resolution guides preparation.

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