Skip to main content
Glama
JackXuyi

Current operating environment

getProxyInfo

Retrieve proxy configuration details from your current network environment to understand connection settings and troubleshoot network access issues.

Instructions

获取当前网络的所有代理信息

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The switch case in handleCallToolRequest that executes the getProxyInfo tool. It reads proxy-related environment variables (HTTP_PROXY, HTTPS_PROXY, NO_PROXY) and returns a JSON-formatted response with their values.
    case "getProxyInfo": {
      const proxyInfo = {
        httpProxy: process.env.HTTP_PROXY || process.env.http_proxy || '未配置',
        httpsProxy: process.env.HTTPS_PROXY || process.env.https_proxy || '未配置',
        noProxy: process.env.NO_PROXY || process.env.no_proxy || '未配置'
      };
    
      return {
        content: [{
          type: "text",
          text: JSON.stringify(proxyInfo, null, 2)
        }]
      };
    }
  • src/index.ts:118-126 (registration)
    The tool definition in the handleRequest function (listTools handler), which lists the getProxyInfo tool with its name, description, and input schema (empty object).
    {
      name: "getProxyInfo",
      description: "获取当前网络的所有代理信息",
      inputSchema: {
        type: "object",
        properties: {},
        required: []
      }
    },
  • The inputSchema definition for the getProxyInfo tool, specifying an empty object schema with no properties or requirements.
    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 what the tool does but lacks details on traits like whether it's read-only, requires permissions, has rate limits, or what format the output takes. 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 that directly states the tool's purpose without any 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.

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 covers the basic purpose but lacks context on usage, behavioral traits, or output, which could be helpful for an agent to make informed decisions, especially with many sibling tools.

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%, so there's no need for parameter details in the description. The description doesn't add parameter semantics, but this is acceptable given the lack of parameters, aligning with the baseline for 0 parameters.

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 action ('获取' meaning 'get') and resource ('当前网络的所有代理信息' meaning 'all proxy information for the current network'), making the purpose specific and understandable. However, it doesn't explicitly differentiate from sibling tools like 'getNetworkInfo' or 'getVpnInfo', which might also relate to network configuration.

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 for system information (e.g., 'getNetworkInfo', 'getVpnInfo'), there's no indication of context, prerequisites, or exclusions, leaving the agent to guess based on the tool 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