Skip to main content
Glama
JackXuyi

Current operating environment

getHardwareInfo

Retrieve hardware information for the current device, including manufacturing date, to analyze system specifications and configuration details.

Instructions

获取当前设备的硬件信息,包括生产日期等

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler case for getHardwareInfo tool that fetches system hardware information using systeminformation library (si.system()) and returns it as JSON text content.
    case "getHardwareInfo": {
      const hardwareInfo = await si.system();
      return {
        content: [{
          type: "text",
          text: JSON.stringify(hardwareInfo, null, 2)
        }]
      };
    }
  • src/index.ts:127-134 (registration)
    Registration of the getHardwareInfo tool in the listTools handler, including name, description, and empty input schema.
    {
      name: "getHardwareInfo",
      description: "获取当前设备的硬件信息,包括生产日期等",
      inputSchema: {
        type: "object",
        properties: {},
        required: []
      }
  • Input schema for getHardwareInfo tool, which takes no parameters.
    inputSchema: {
      type: "object",
      properties: {},
      required: []
    }
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states it 'gets' information, implying a read-only operation, but doesn't clarify if this requires permissions, what format the output is in, or any rate limits. For a tool with zero annotation coverage, this is a significant gap, as it lacks details on safety, performance, or response behavior.

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 a single, concise sentence: '获取当前设备的硬件信息,包括生产日期等'. It's front-loaded with the core purpose and adds a brief scope. There's no wasted text, but it could be slightly more structured by explicitly mentioning output or context, though not required for full marks.

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

Completeness2/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, no annotations, and no output schema, the description is incomplete. It doesn't explain what 'hardware information' entails beyond 'production date', how it differs from siblings, or what the return format is. For a tool in a crowded namespace with no structured support, more context is needed to guide effective use.

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 0 parameters, and the schema description coverage is 100% (since there are no parameters to describe). The description doesn't need to add parameter semantics, so it meets the baseline of 4 for tools with no parameters. It efficiently avoids unnecessary parameter details.

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 clearly states the tool's purpose: '获取当前设备的硬件信息,包括生产日期等' (Get current device hardware information, including production date, etc.). It specifies the verb '获取' (get) and resource '硬件信息' (hardware information), with additional scope '包括生产日期等' (including production date, etc.). However, it doesn't explicitly distinguish this tool from its many siblings (e.g., getCpuInfo, getMemoryInfo), which are also hardware-related, making it less specific than a perfect 5.

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

Usage Guidelines2/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 versus alternatives. With many sibling tools like getCpuInfo, getMemoryInfo, and getGraphicsInfo, it's unclear if this tool aggregates multiple hardware aspects or overlaps with them. There's no mention of prerequisites, context, or exclusions, leaving the agent to guess based on the name alone.

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/JackXuyi/env-mcp'

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