Skip to main content
Glama
JackXuyi

Current operating environment

getPlatformInfo

Retrieve system platform details like OS type, version, and architecture to configure applications or diagnose compatibility issues.

Instructions

获取当前系统的平台信息

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for the 'getPlatformInfo' tool, which collects platform details using Node.js 'os' module and returns them as JSON.
    case "getPlatformInfo": {
      const platformInfo = {
        platform: os.platform(),
        arch: os.arch(),
        hostname: os.hostname(),
        type: os.type(),
        release: os.release(),
        version: os.version()
      };
    
      return {
        content: [{
          type: "text",
          text: JSON.stringify(platformInfo, null, 2)
        }]
      };
    }
  • Schema definition for the 'getPlatformInfo' tool, specifying an empty input object schema.
    name: "getPlatformInfo",
    description: "获取当前系统的平台信息",
    inputSchema: {
      type: "object",
      properties: {},
      required: []
    }
  • src/index.ts:28-36 (registration)
    Registration of the 'getPlatformInfo' tool in the list of tools returned by ListToolsRequestHandler.
    {
      name: "getPlatformInfo",
      description: "获取当前系统的平台信息",
      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 full burden. It states the tool retrieves information (implying read-only), but doesn't disclose behavioral traits like whether it requires permissions, returns structured data, has rate limits, or what 'platform' specifically includes (OS, architecture, etc.). This is inadequate for a tool with zero annotation coverage.

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, efficient sentence in Chinese that directly states the tool's purpose with no wasted words. It's appropriately sized and front-loaded, making it easy to parse quickly.

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 lack of annotations and output schema, the description is incomplete. It doesn't explain what 'platform information' includes (e.g., OS name, version, architecture), the return format, or how it differs from other system info tools. For a tool in a crowded sibling set, more context is needed to guide proper usage.

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% (empty schema). The description doesn't need to add parameter semantics, so it meets the baseline of 4 for zero-parameter tools. No additional parameter context is required or provided.

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 as '获取当前系统的平台信息' (get current system platform information), which specifies the verb (get) and resource (platform information). It distinguishes from siblings by focusing on 'platform' rather than specific hardware/software components, though it doesn't explicitly differentiate from tools like getHardwareInfo or getNodeInfo.

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 retrieving system information (e.g., getHardwareInfo, getCpuInfo, getNodeInfo), there's no indication of what 'platform information' encompasses or when it's preferred over other tools.

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