Skip to main content
Glama
JackXuyi

Current operating environment

getGraphicsInfo

Retrieve detailed graphics card specifications from the current device to identify hardware capabilities and troubleshoot display issues.

Instructions

获取当前设备的显卡信息

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler for the 'getGraphicsInfo' tool. It uses the 'systeminformation' library (si.graphics()) to fetch graphics card information and returns it as a JSON-formatted text response.
    case "getGraphicsInfo": {
      const graphicsInfo = await si.graphics();
      return {
        content: [{
          type: "text",
          text: JSON.stringify(graphicsInfo, null, 2)
        }]
      };
    }
  • src/index.ts:199-207 (registration)
    The registration of the 'getGraphicsInfo' tool in the list of available tools returned by handleRequest. Includes name, description, and input schema (empty object).
    {
      name: "getGraphicsInfo",
      description: "获取当前设备的显卡信息",
      inputSchema: {
        type: "object",
        properties: {},
        required: []
      }
    },
  • The input schema for the 'getGraphicsInfo' tool, which requires no parameters (empty object). Part of the tool registration.
    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 retrieves information ('获取'), implying a read-only operation, but doesn't specify details like whether it requires admin permissions, what format the output is in (e.g., JSON, text), potential rate limits, or if it works across all platforms. For a tool with zero annotation coverage, this leaves significant gaps in understanding its behavior and constraints.

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 a single, clear sentence in Chinese: '获取当前设备的显卡信息'. It is front-loaded with the core action and resource, with zero wasted words. Every part of the sentence directly contributes to understanding the tool's purpose, making it highly efficient and well-structured.

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

Completeness3/5

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

Given the tool's simplicity (0 parameters, no output schema, no annotations), the description is minimally complete. It states what the tool does but lacks context on usage, behavioral details, or output format. For a basic read operation, this might be adequate, but it doesn't fully compensate for the absence of annotations or output schema, leaving the agent to infer behavior from the name alone.

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 schema description coverage is 100% (since there are no parameters to describe). The description doesn't need to add parameter semantics, as there are none to explain. A baseline score of 4 is appropriate for a parameterless tool, as the description adequately conveys the action without unnecessary complexity.

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 '获取当前设备的显卡信息' (Get current device's graphics card information) clearly states the verb ('获取' - get) and resource ('显卡信息' - graphics card information), making the purpose immediately understandable. It distinguishes from siblings by specifying graphics hardware rather than CPU, memory, network, etc. However, it doesn't explicitly contrast with other hardware-related tools like getHardwareInfo, which might cover broader hardware details.

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. It doesn't mention prerequisites (e.g., requires graphics hardware), exclusions (e.g., not for virtual machines without GPUs), or comparisons to siblings like getHardwareInfo (which might include graphics info). Usage is implied only by the tool name and description, with no explicit context for selection.

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