Skip to main content
Glama

check

Verify available quantization backends and hardware compatibility for model compression. Reports installed engines (GGUF/GPTQ/AWQ), GPU support, and system resources.

Instructions

Check available quantization backends on this system.

Reports which quantization engines (GGUF/GPTQ/AWQ) are installed, whether PyTorch and transformers are available, GPU information (CUDA or Apple MPS), and system RAM.

No arguments required. Lightweight system check.

Returns: Dictionary of available backends and hardware info.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The `check` tool handler, which checks available quantization backends, PyTorch/transformers versions, and hardware information. It calls `check_dependencies` to gather system details.
    def check() -> dict[str, Any]:
        """Check available quantization backends on this system.
    
        Reports which quantization engines (GGUF/GPTQ/AWQ) are installed,
        whether PyTorch and transformers are available, GPU information
        (CUDA or Apple MPS), and system RAM.
    
        No arguments required. Lightweight system check.
    
        Returns:
            Dictionary of available backends and hardware info.
        """
        deps = check_dependencies()
    
        backends = {
            "gguf": {
                "available": deps.get("gguf", False),
                "install": "pip install llama-cpp-python",
            },
            "gptq": {
                "available": deps.get("gptq", False),
                "install": "pip install auto-gptq datasets",
            },
            "awq": {
                "available": deps.get("awq", False),
                "install": "pip install autoawq",
            },
        }
    
        hardware = {
            "platform": deps.get("platform", "unknown"),
            "arch": deps.get("arch", "unknown"),
            "system_ram_gb": deps.get("system_ram_gb", 0),
        }
    
        if deps.get("cuda"):
            hardware["gpu"] = deps.get("gpu_name", "CUDA GPU")
            hardware["gpu_mem_gb"] = deps.get("gpu_mem_gb", 0)
            hardware["accelerator"] = "cuda"
        elif deps.get("mps"):
            hardware["accelerator"] = "mps"
            hardware["gpu"] = "Apple Silicon (Metal Performance Shaders)"
        else:
            hardware["accelerator"] = "cpu"
    
        core = {
            "torch": {
                "available": deps.get("torch", False),
                "version": deps.get("torch_version", None),
                "install": "pip install torch",
            },
            "transformers": {
                "available": deps.get("transformers", False),
                "version": deps.get("transformers_version", None),
                "install": "pip install transformers",
            },
        }
    
        return {
            "backends": backends,
            "core_dependencies": core,
            "hardware": hardware,
            "server_version": __version__,
        }
Behavior4/5

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

With no annotations provided, the description carries the full burden. It successfully discloses what information is gathered (specific backend engines, GPU type, RAM), notes the zero-argument nature, and characterizes the operation as 'lightweight', implying minimal resource impact. However, it stops short of explicitly stating idempotency or read-only safety.

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?

The description is well-structured with clear information hierarchy: purpose statement first, followed by detailed reporting scope, usage constraints, and return type. Every sentence provides necessary context without redundancy.

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?

Given the tool's low complexity (no parameters) and presence of an output schema, the description adequately covers the return value shape (Dictionary) and inspection scope. It could be improved by explicitly stating safety properties (non-destructive) given the lack of annotations, but remains functionally 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?

With zero parameters and 100% schema coverage, the baseline is 4. The description adds value by explicitly confirming 'No arguments required', reinforcing the schema structure for the agent.

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?

The description opens with a specific verb ('Check') and clearly identifies the resource (quantization backends, PyTorch, GPU, RAM). It effectively distinguishes from action-oriented siblings like 'quantize', 'push', and 'evaluate' by focusing on system inspection rather than model manipulation.

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?

The description notes 'No arguments required' and 'Lightweight system check', which implies usage context (quick diagnostic vs heavy operations), but lacks explicit guidance on when to use this versus siblings like 'info' or as a prerequisite to 'quantize'.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ShipItAndPray/mcp-turboquant'

If you have feedback or need assistance with the MCP directory API, please join our Discord server