Skip to main content
Glama
ygdcz

simple-MCP

by ygdcz
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

simple-MCP

一个最小的 MCP (Model Context Protocol) server 示例,通过 stdio 暴露一个查询本机硬件信息的工具。

依赖

  • Python >= 3.13

  • uv

Related MCP server: mcpscope

安装

uv sync

运行

uv run main.py

server 以 stdio 传输方式启动,等待 MCP 客户端连接。

工具

get_host_info

无参数,返回结构化的主机信息:

字段

类型

说明

system

string

操作系统名称,如 Darwin / Linux / Windows

release

string

内核版本号

machine

string

CPU 架构,如 x86_64 / arm64

processor

string

处理器标识,部分平台可能为空

memory_gb

number

物理内存总量,单位 GB

cpu_count

integer

逻辑核心数,无法探测时为 -1

cpu_model

string

CPU 型号名称,无法探测时为 Unknown

返回类型是 pydantic model HostInfo,MCP 会据此生成自描述的 output schema,客户端无需解析字符串。

CPU 型号按平台探测:macOS 用 sysctl machdep.cpu.brand_string,Linux 读 /proc/cpuinfo,Windows 读 PROCESSOR_IDENTIFIER,全部失败时回退到 platform 模块。

客户端配置

{
  "mcpServers": {
    "hostInfoMcp": {
      "command": "uv",
      "args": ["--directory", "/path/to/simple-MCP", "run", "main.py"]
    }
  }
}

本地验证

uv run tools.py    # 直接打印主机信息 JSON

Available Tools

1 tool
get_host_infoA

获取本机硬件与操作系统信息。

返回 system(系统名)、release(内核版本)、machine(架构)、 processor(处理器标识)、memory_gb(总内存 GB)、 cpu_count(逻辑核心数)、cpu_model(CPU 型号)。

ParametersJSON Schema
NameRequiredDescriptionDefault

No parameters

Output Schema

ParametersJSON Schema
NameRequiredDescription
systemYes操作系统名称,如 Darwin / Linux / Windows
machineYesCPU 架构,如 x86_64 / arm64
releaseYes内核版本号
cpu_countYes逻辑核心数,无法探测时为 -1
cpu_modelYesCPU 型号名称,无法探测时为 Unknown
memory_gbYes物理内存总量,单位 GB
processorYes处理器标识,部分平台可能为空

TDQS

A3.9/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 burden. It lists what fields are returned, but does not disclose potential side effects (none expected), authentication requirements, or performance implications. The description is adequate for a read-only info tool but lacks depth.

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?

The description is brief (two lines plus a bullet list) and well-structured. Every sentence adds value. It could be slightly more concise, but overall efficient.

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 has no parameters, an output schema exists (per context), and no siblings, the description covers all necessary information: purpose and return fields. It is complete for a simple info retrieval tool, though it omits example output or error conditions.

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?

There are zero parameters, so the input schema provides no information. The description compensates by explicitly listing the returned fields (system, release, machine, etc.) with their meanings, adding value beyond the schema.

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 clearly states the tool retrieves local host hardware and OS information, listing specific fields. The verb 'get' combined with 'host info' is specific and unambiguous. No sibling tools exist, so differentiation is not required.

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 provides no guidance on when to use this tool vs alternatives or any exclusions. However, the tool is simple with no siblings, so the lack of explicit guidelines is acceptable but minimal.

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

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. 1 tool updatev0.1.0
    • First observedget_host_info
Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

A4.1/5.0
Disambiguation5/5

With only one tool, there is no possibility of confusion with other tools. The tool's purpose is clearly defined.

Naming Consistency5/5

The single tool follows a clear verb_noun pattern (get_host_info), which is consistent and descriptive.

Tool Count3/5

One tool is on the low end, but given the server's name 'simple-MCP', it is reasonable for a focused purpose. However, it is borderline for general utility.

Completeness5/5

The tool returns comprehensive host hardware and OS information (system, kernel, architecture, processor, memory, CPU), covering the domain well with no obvious gaps.

Maintenance

ActivitySlowing
ResponsivenessSyncing

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

  • mcp-cli-catalog

    abcpro1
    A
    license
    Not graded
    quality
    D
    maintenance
    An MCP server that publishes CLI tools on your machine for discoverability by LLMs
    14
    1
    MIT

  • mcpscope

    sla10132000
    F
    license
    A
    quality
    D
    maintenance
    A simple local MCP server that provides greeting and integer addition tools.
    2
    -

  • ai-mcp

    wangyj641
    F
    license
    A
    quality
    D
    maintenance
    Lightweight MCP server that exposes tools for system information and weather lookup, designed for agent integration via stdio.
    1
    -

  • hello-world-mcp

    emokhtareg
    A
    license
    A
    quality
    C
    maintenance
    A minimal MCP server that provides a single 'hello' tool returning 'Hello, world!'.
    2
    16
    MIT

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/ygdcz/simple-MCP'

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