Skip to main content
Glama

ExducerAI GPU cloud

One deployment

get_deployment
Read-onlyIdempotent

One deployment in full: state and reason, SSH host and port, the host key fingerprint to verify, rate per GPU-hour, cost so far, start and end time, endpoints.

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": {
      "id": "<id>"
    },
    "name": "get_deployment"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe deployment id (rnt_… on a live key, snd_… in the sandbox).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so safety is covered structurally. The description adds real content beyond that by naming the returned data — notably that it exposes a host key fingerprint, SSH coordinates, and accumulated cost, which signals sensitivity. It does not say what happens for an unknown id, whether stopped/destroyed deployments are still retrievable, or how fresh the cost figure is.

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 sentence with the identifying phrase front-loaded and a colon-led field list that carries only substantive content. No filler, no restatement of the title.

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?

With no output schema, the description correctly takes on the burden of describing return values and does so thoroughly. What remains thin is the operational edge: retrieval of non-existent or terminated deployments and the relationship to id-discovery siblings, which matters for a look-up 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?

Schema description coverage is 100% and the schema already explains the id format, the rnt_/snd_ prefix convention, and the pattern constraint. The description adds no additional meaning about the id argument, so the 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 resource retrieval ('One deployment in full') and then enumerates the exact payload fields — state and reason, SSH host/port, host key fingerprint, rate per GPU-hour, cost, times, endpoints. That distinguishes it clearly from list_deployments (multiple, summarized) and get_deployment_events (lifecycle history) without opening either schema.

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?

'In full' implies this is the detail view as opposed to the list view, so usage is implied rather than stated. It never says when to prefer it over get_deployment_events or wait_for_deployment, nor that an id is typically obtained from list_deployments, and it gives no exclusion cases.

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