Skip to main content
Glama

Servers

list_servers
Read-onlyIdempotent

Retrieve the cloud servers on a GoMami account, with pagination controls for page number and results per page.

Instructions

List the servers on the account.

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

Input Schema

NameRequiredDescriptionDefault
pageNoPage number, starting at 1
resultsNoResults per page (default 20, max 200)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, covering the safety profile. The description adds only 'on the account', which is essentially the implicit scope of every tool here, and says nothing about pagination behavior, result volume, or ordering that a lister tool would benefit from.

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?

A single front-loaded sentence with no filler, which is structurally clean. Its brevity borders on under-specification, but it contains no wasted wording.

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

Completeness2/5

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

For a zero-required-parameter list tool the call itself is easy, but the description omits result volume, pagination expectations and how a server record relates to get_server. With no output schema, the description should carry more of that burden than one sentence does.

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 both parameters (page, results with default 20 / max 200) are fully documented in the schema. The description adds no paging semantics of its own, so the baseline 3 is appropriate.

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 gives a specific verb and resource ('List the servers') plus a scope ('on the account'), so an agent immediately knows what it retrieves. It does not differentiate itself from siblings such as get_server or verify_connection, but the core purpose is unambiguous.

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 statement of when to use this versus get_server (single server lookup) or the other list_* tools, and no note on when the paginated list is appropriate. The agent must infer usage entirely from the tool name.

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