Skip to main content
Glama

getAllValues

Retrieve all rule values from the Whistle MCP Server to manage and control local proxy configurations efficiently.

Instructions

获取所有规则的值

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Core handler function that executes the logic for getting all values from the Whistle server. Makes a GET request to /cgi-bin/init with timestamp param and extracts values.list from the response.
    async getAllValues(): Promise<any> {
      const timestamp = Date.now();
      const response = await axios.get(`${this.baseUrl}/cgi-bin/init`, {
        params: { _: timestamp },
        headers: {
          Accept: "application/json, text/javascript, */*; q=0.01",
          "Cache-Control": "no-cache",
          Pragma: "no-cache",
          "X-Requested-With": "XMLHttpRequest",
        },
      });
      const { data } = response;
      const {
        values: { list },
      } = data;
      return list || [];
    }
  • src/index.ts:187-195 (registration)
    Registers the MCP tool 'getAllValues' with name, description, empty input schema (z.object({})), and execute handler that delegates to whistleClient.getAllValues() and formats the response.
    server.addTool({
      name: "getAllValues",
      description: "获取所有规则的值",
      parameters: z.object({}),
      execute: async () => {
        const rules = await whistleClient.getAllValues();
        return formatResponse(rules);
      },
    });
  • Zod schema definition for the tool inputs: empty object since no parameters are required.
    parameters: z.object({}),
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 a read operation ('获取' - get), implying it's likely non-destructive, but doesn't disclose behavioral traits such as permissions needed, rate limits, response format, or whether it returns all values at once (e.g., pagination). This is inadequate for a tool with no 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence in Chinese ('获取所有规则的值'), which is appropriately concise and front-loaded. There's no wasted text, though it could benefit from more detail given the lack of other context.

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 no annotations, no output schema, and low complexity (0 parameters), the description is incomplete. It doesn't explain what 'rules' and 'values' mean in this system, the return format, or how it differs from similar tools like 'getRules'. For a read operation in a server with many siblings, more context is needed.

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% (though empty). The description doesn't add parameter details since there are none, which is appropriate. Baseline is 4 for 0 parameters, as no compensation is needed.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description '获取所有规则的值' (Get all rule values) states a verb ('获取' - get) and resource ('规则的值' - rule values), providing a basic purpose. However, it's vague about what 'rules' and 'values' refer to in this context, and it doesn't distinguish from siblings like 'getRules' or 'getInterceptInfo'. It avoids tautology but lacks specificity.

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, context, or exclusions, and with siblings like 'getRules' available, there's no indication of how this differs (e.g., whether it retrieves values only vs. full rule details). This leaves usage unclear.

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

Related 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/7gugu/whistle-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server