Skip to main content
Glama

ExducerAI GPU cloud

Deployments

list_deployments
Read-onlyIdempotent

Every deployment of the account with its state, GPU count, rate, cost so far and end time. States: requested, queued, provisioning, running, then stopped, ended, failed or cancelled.

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_deployments"
  }
}

Input Schema

NameRequiredDescriptionDefault
include_sandboxNoOn a live key, also list sandbox deployments.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description's job is to add substance — and it does, by enumerating the returned attributes and the full state lifecycle (requested → queued → provisioning → running → stopped/ended/failed/cancelled). That lifecycle is genuinely useful for interpreting results. It stops short of disclosing pagination, ordering, or whether terminal deployments remain in the list indefinitely.

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 sentences, zero filler: the first front-loads what is returned, the second supplies the state vocabulary. Nothing is redundant with the title or annotations.

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, so the description usefully compensates by naming the returned fields and valid state values. The remaining gaps — result volume/pagination, ordering, and how the sandbox flag interacts with 'every deployment' — are minor for a zero-required-parameter read tool.

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?

With a single parameter and 100% schema description coverage, the schema already explains include_sandbox ('On a live key, also list sandbox deployments'). The description says 'Every deployment of the account' without clarifying whether sandbox deployments are included by default, which is the one ambiguity the parameter introduces. Baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific resource and scope: 'Every deployment of the account', plus the fields returned (state, GPU count, rate, cost so far, end time). It is clearly a bulk listing rather than a single-record fetch, but it never names the sibling it is distinct from (get_deployment), so differentiation is left to the reader.

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 by 'Every deployment of the account' — an agent can infer this is the enumeration call versus get_deployment or get_deployment_events, but there is no explicit when-to-use or when-not-to-use statement. No preconditions, key requirements, or alternatives are mentioned.

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.

Resources