Skip to main content
Glama
Sign In
arch-mcp-server

arch-mcp-server

by DankyoDev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Host capabilities

host_capabilities
Read-onlyIdempotent

Discover which tools and features a Linux host supports at startup, then check it before calling potentially unsupported commands.

Instructions

Which tools and features this host has (pacman, journald, sensors, nftables, AUR...), detected once at startup. Use it before calling a tool that may be unsupported.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint=false, so the safety profile is covered. The description adds genuinely non-redundant context: the capability set is 'detected once at startup,' telling the agent the result is a cached snapshot that won't change mid-session. It doesn't say what the payload looks like beyond the examples, which is the remaining gap.

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 short sentences, with the identity of the resource front-loaded and the usage rule second. Every clause carries information: examples, detection timing, and the call trigger. Nothing is 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?

With no output schema, the description carries the burden of describing the return, and it does so at a high level via the capability examples plus the startup-detection caveat. It would be stronger if it indicated the shape of the response (e.g., named capability flags or a list), but an agent has enough to call it correctly.

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; the baseline for a no-param tool applies. The description correctly implies a parameterless, take-no-arguments call by never referencing inputs.

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 uses a clear verb-plus-resource framing ('which tools and features this host has') and grounds it with concrete examples (pacman, journald, sensors, nftables, AUR), so an agent knows this is a capability inventory rather than a general system-info dump. It does not explicitly contrast itself with siblings like sys_info or sys_status, which keeps it short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives an explicit call condition: 'Use it before calling a tool that may be unsupported.' That is actionable pre-flight guidance. It stops short of a 5 because there is no negative guidance (e.g., don't call it per-invocation, or what to do if a capability is absent).

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