Skip to main content
Glama
Sign In

NEXUS AI

by io.github.nexusrun
OverviewDiscussions(2)Admin

List Deployments

nexusai_deploy_list
Read-only

Lists deployments available to the authenticated tenant.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum rows to return. Default 20.
offsetNoPagination offset. Default 0.
statusNoOptional status filter (queued|deploying|running|failed|terminated).
providerNoOptional provider filter (docker|gcp_cloud_run|aws_app_runner|azure_container_apps).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / provider / description
      Previous value: -"Optional provider filter (docker|gcp_cloud_run|aws_ecs_fargate|azure_container_apps)."New value: +"Optional provider filter (docker|gcp_cloud_run|aws_app_runner|azure_container_apps)."
  2. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description's only added behavioral fact is the tenant-scoping of results, which is useful but thin; it says nothing about ordering, empty results, or pagination behavior.

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?

A single front-loaded sentence with zero waste. Nothing redundant is stated, though the brevity reflects under-specification rather than efficiency gained by schema coverage.

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

Completeness3/5

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

For a read-only list tool with a fully documented schema and clear annotations, the essentials are present. Gaps remain around result ordering, whether filters are AND-combined, and the shape of returned deployment objects, which matters since no output schema exists.

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?

Schema description coverage is 100%, so all four parameters (limit, offset, status, provider) are already documented with defaults and allowed values. The description adds nothing beyond that, which is the baseline case rather than a deficiency.

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?

States a specific verb+resource ('Lists deployments') and scopes it to the authenticated tenant, which is real information beyond the name. It does not, however, distinguish itself from close siblings such as nexusai_deploy_status or nexusai_deploy_health, so the agent must infer when a list is preferable to a status check.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to call this versus nexusai_deploy_status or nexusai_deploy_health, no mention of filter combinations, and no stated prerequisites beyond the tenant scoping. Usage is left entirely to inference from the name.

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

All NEXUS AI toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources