Skip to main content
Glama
JackXuyi

Current operating environment

getBluetoothInfo

Retrieve Bluetooth device information from the current operating environment to access connection status and hardware details.

Instructions

获取当前设备的蓝牙信息

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler implementation for the 'getBluetoothInfo' tool. It uses the 'systeminformation' library (si.bluetoothDevices()) to retrieve Bluetooth device information and returns it as a JSON-formatted text response.
    case "getBluetoothInfo": {
      const bluetoothInfo = await si.bluetoothDevices();
      return {
        content: [{
          type: "text",
          text: JSON.stringify(bluetoothInfo, null, 2)
        }]
      };
    }
  • src/index.ts:218-225 (registration)
    Tool registration in the listTools response, including the tool name, description, and input schema (empty object, no parameters required).
      name: "getBluetoothInfo",
      description: "获取当前设备的蓝牙信息",
      inputSchema: {
        type: "object",
        properties: {},
        required: []
      }
    },
  • Input schema definition for the 'getBluetoothInfo' tool, specifying an empty object (no input parameters).
    inputSchema: {
      type: "object",
      properties: {},
      required: []
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states it retrieves Bluetooth information but doesn't specify whether this requires permissions, what format the information is returned in, whether it's real-time or cached data, or if there are any rate limits or side effects. For a system information tool with zero annotation coverage, this leaves significant behavioral questions unanswered.

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 zero wasted words. It's appropriately sized for a simple retrieval tool and front-loads the essential information without unnecessary elaboration.

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 annotations, no output schema), the description is minimally complete. It tells the agent what information will be retrieved but doesn't provide details about the return format, data structure, or potential limitations. For a system information tool among many similar siblings, more context about what specific Bluetooth data is included would be helpful.

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 with 100% schema description coverage, so the schema already fully documents the parameter situation. The description appropriately doesn't discuss parameters since none exist. This meets the baseline expectation for a parameterless tool, though it doesn't add any extra context about why no parameters are needed.

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 Bluetooth information) clearly states the verb '获取' (get) and resource '蓝牙信息' (Bluetooth information), making the purpose immediately understandable. It distinguishes from siblings by specifying Bluetooth rather than other system information types like battery, CPU, or network. However, it doesn't specify what specific Bluetooth information is retrieved, which prevents a perfect score.

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. While the name implies it's for Bluetooth information specifically, there's no explicit comparison to other tools like getNetworkInfo or getWifiInfo that might provide related connectivity data. No prerequisites, limitations, or recommended contexts are mentioned.

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