Skip to main content
Glama
JackXuyi

Current operating environment

getAudioInfo

Retrieve audio device information from the current operating environment to identify available hardware and configurations.

Instructions

获取当前设备的音频设备信息

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler for the getAudioInfo tool. It uses si.audio() from the systeminformation library to fetch audio device information and returns it as a JSON-formatted text response.
    case "getAudioInfo": {
      const audioInfo = await si.audio();
      return {
        content: [{
          type: "text",
          text: JSON.stringify(audioInfo, null, 2)
        }]
      };
    }
  • src/index.ts:226-234 (registration)
    Registration of the getAudioInfo tool in the listTools response, including its name, description, and empty input schema.
    {
      name: "getAudioInfo",
      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 the full burden. It states it 'gets' information, implying a read-only operation, but doesn't disclose behavioral traits such as whether it requires permissions, if it's real-time or cached, potential errors (e.g., no audio devices), or output format. For a tool with zero annotation coverage, this is a significant gap in transparency.

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: '获取当前设备的音频设备信息'. It is front-loaded with the core action and resource, with no wasted words. Every part earns its place by specifying the verb, scope, and target.

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 has 0 parameters, 100% schema coverage, no annotations, and no output schema, the description is minimally complete. It states what the tool does but lacks details on output (e.g., what audio info is returned), error handling, or dependencies. For a simple info-fetching tool, this is adequate but leaves gaps that could hinder an agent's understanding.

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, so it meets the baseline of 4 for zero-parameter tools. No additional value is required beyond stating the purpose.

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 audio device information) clearly states the verb ('获取' - get) and resource ('音频设备信息' - audio device information), with scope ('当前设备' - current device). It distinguishes from siblings like getBatteryInfo or getMemoryInfo by specifying audio devices. It loses a point for not being more specific about what 'audio device information' includes (e.g., devices, volume, status).

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 audio hardware), exclusions (e.g., not for network audio), or related tools (e.g., use getHardwareInfo for general hardware details). The context is implied (when audio info is needed), but no explicit usage rules are given.

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