Skip to main content
Glama

Server details

get_server
Read-onlyIdempotent

Retrieves a cloud server's configuration, network details, and traffic period by server ID. Set state=true to also include the server's live state for real-time status checks.

Instructions

Read a server's configuration, network and traffic period. Set state=true to include its live state.

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": {
      "serverId": "<serverId>"
    },
    "name": "get_server"
  }
}

Input Schema

NameRequiredDescriptionDefault
stateNoInclude the live server state
serverIdYesServer ID (UUID) from list_servers

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and non-destructive, so the safety profile is covered. The description adds useful content about what the read returns (configuration, network, traffic period) and clarifies that live state is opt-in via state=true, though it says nothing about auth, rate limits or error 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?

Two sentences, front-loaded with the main read scope and followed by the one optional flag that changes behavior. Nothing redundant or padded.

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?

For a simple two-parameter read with no output schema, the description enumerates the returned data areas and the opt-in flag, which is close to what an agent needs. Minor gap: no explicit tie-in to list_servers workflow or output shape.

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 coverage is 100%, so both parameters are already documented, and the description's 'set state=true' essentially restates the schema text for state. It adds marginal framing (live state is a separate concern from stored config) but no format or edge-case detail beyond the schema.

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?

Specific verb ('Read') plus resource ('a server's configuration, network and traffic period') tells the agent exactly what comes back and that it targets a single server, which separates it from list_servers. It stops short of naming that sibling directly.

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 implied rather than stated: the required serverId and the schema hint ('from list_servers') suggest the list-then-detail flow, but the description never says when to pick this over list_servers or another get_* tool.

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