Skip to main content
Glama
Local AI MCP

Local AI MCP

Official
by TMHSDigital

System resources

system_resources
Read-onlyIdempotent

Report local CPU, RAM, platform, and GPU/VRAM details to check whether your machine can run a given local AI model.

Instructions

Report local hardware: platform, total/available RAM, CPU count, and GPUs with total/free VRAM (NVIDIA via nvidia-smi, AMD/Intel via sysfs or the Windows registry, Apple Silicon unified memory). Each GPU names its data source.

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": "system_resources"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
gpusYes
cpuCountYes
platformYes
ramFreeBytesYes
ramTotalBytesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.5.0
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "http://json-schema.org/draft-07/schema#",
      +  "additionalProperties": false,
      +  "properties": {
      +    "cpuCount": {
      +      "type": "number"
      +    },
      +    "gpus": {
      +      "items": {
      +        "additionalProperties": {},
      +        "propertyNames": {
      +          "type": "string"
      +        },
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "platform": {
      +      "type": "string"
      +    },
      +    "ramFreeBytes": {
      +      "type": "number"
      +    },
      +    "ramTotalBytes": {
      +      "type": "number"
      +    }
      +  },
      +  "required": [
      +    "platform",
      +    "ramTotalBytes",
      +    "ramFreeBytes",
      +    "cpuCount",
      +    "gpus"
      +  ],
      +  "type": "object"
      +}
  2. First observedv0.4.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description adds genuinely new context beyond that: the per-platform discovery mechanisms (nvidia-smi, sysfs, Windows registry, Apple Silicon unified memory) and the guarantee that each GPU reports its data source, which tells the agent how much to trust the VRAM figures.

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?

Two dense sentences, front-loaded with the returned fields before the platform-detection detail. Every clause carries information, though the parenthetical enumeration of OS-specific mechanisms is heavy for a definition whose output schema already documents the shape.

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

Completeness5/5

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

With an output schema present, the description need not describe return structure, and it still previews the key fields and the data-source provenance. For a zero-parameter, read-only inventory tool, nothing an agent needs in order to call it correctly is missing.

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 takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The description correctly implies a parameterless call with no scoping options.

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 verb ("Report") and resource ("local hardware") and enumerates exactly what is returned: platform, total/available RAM, CPU count, GPUs with total/free VRAM. This is unmistakably distinct from the sibling set, which is entirely model-management and inference tooling; no sibling could be confused with a hardware inventory read.

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 only implied: an agent can infer this is the tool to consult for host capacity, but the description never says when to reach for it versus siblings like health_check, fit_check, or list_providers. No exclusions or prerequisites are stated.

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