Skip to main content
Glama
Sign In
GPU Manager MCP

GPU Manager MCP

by quxlzx
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

list_gpus

Discovers all NVIDIA, AMD, and Intel GPUs and returns stable IDs, names, VRAM totals, PCI bus IDs, driver versions, and telemetry capabilities for device inventory and monitoring.

Instructions

Discover all GPUs (NVIDIA/AMD/Intel). Returns stable gpu_ids, names, VRAM totals, PCI bus ids, driver versions and supported telemetry capabilities per device.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are provided, so the description carries the behavioral burden. It discloses scope and returned fields (IDs, names, VRAM, PCI bus ids, drivers, telemetry capabilities), but does not explicitly state that it is read-only, side-effect free, ordered, or paginated.

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 action and followed by concrete return fields. Every clause earns its place and there is no filler.

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 low-complexity, zero-parameter inventory tool with no output schema, the description lists key return values and makes the call self-contained. The lack of explicit sibling routing and read-only constraints keeps it from being fully complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has zero parameters, so the baseline is 4. The description adds no parameter meaning because there are no parameters to clarify.

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 ('Discover') and resource ('all GPUs'), including vendor coverage and return fields. It distinguishes itself from metric-specific siblings as an inventory/list tool, but does not explicitly contrast with get_gpu_info or get_system_gpu_summary.

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?

Implies this is the discovery/enumeration starting point because it returns stable gpu_ids, but gives no explicit when-to-use or when-not guidance. It also does not route the agent to alternatives such as get_gpu_info for per-device details or get_system_gpu_summary for summaries.

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

Deploy Server

Other Tools