Skip to main content
Glama
billyfranklim1

mcp-evolution

Fetch Privacy Settings

fetch_privacy

Fetch the current privacy settings of a pinned WhatsApp instance for review or verification.

Instructions

Fetch the current privacy settings of the pinned WhatsApp instance.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The main handler function for the 'fetch_privacy' tool. It registers the tool with the MCP server, defining an empty inputSchema, and on execution calls the Evolution API endpoint `/chat/fetchPrivacySettings/{instanceName}` to fetch privacy settings, returning the result as JSON.
    export function registerFetchPrivacy(server: McpServer, client: EvolutionClient): void {
      server.registerTool(
        "fetch_privacy",
        {
          title: "Fetch Privacy Settings",
          description: "Fetch the current privacy settings of the pinned WhatsApp instance.",
          inputSchema: {},
        },
        async () => {
          try {
            const data = await client.get(`/chat/fetchPrivacySettings/${client.instanceName}`);
            return { content: [{ type: "text" as const, text: JSON.stringify(data, null, 2) }] };
          } catch (e) {
            if (e instanceof McpError) return { isError: true, content: [{ type: "text" as const, text: e.message }] };
            throw e;
          }
        }
      );
    }
  • The tool registration via server.registerTool('fetch_privacy', ...) which wires the tool name to its schema and handler.
    server.registerTool(
      "fetch_privacy",
      {
        title: "Fetch Privacy Settings",
        description: "Fetch the current privacy settings of the pinned WhatsApp instance.",
        inputSchema: {},
      },
      async () => {
        try {
          const data = await client.get(`/chat/fetchPrivacySettings/${client.instanceName}`);
          return { content: [{ type: "text" as const, text: JSON.stringify(data, null, 2) }] };
        } catch (e) {
          if (e instanceof McpError) return { isError: true, content: [{ type: "text" as const, text: e.message }] };
          throw e;
        }
      }
    );
  • Import of registerFetchPrivacy from the fetch-privacy module.
    import { registerFetchPrivacy } from "./fetch-privacy.js";
  • Registration call registerFetchPrivacy(server, client) invoked in registerAllTools.
    registerFetchPrivacy(server, client);
Behavior2/5

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

Without annotations, the description carries the full burden. It states 'Fetch' implying a read-only operation but lacks details on rate limits, authentication requirements, or any potential side effects, which are minimal but not clarified.

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 sentence that is concise, front-loaded with the verb and resource, and contains no redundant words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the simplicity (no parameters, no output schema) and the presence of sibling tools, the description is mostly complete. However, it could mention what specific privacy settings are retrieved to improve clarity.

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 zero parameters, and the input schema adequately covers this. Per guidelines, baseline is 4; the description does not need to add parameter information.

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

Purpose5/5

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

The description clearly states the verb 'Fetch', the resource 'privacy settings', and the scope 'pinned WhatsApp instance', distinguishing it from sibling tools like 'update_privacy' (write) and 'get_settings' (broader).

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?

No guidance is provided on when to use this tool versus alternatives such as 'get_settings' for general settings or 'update_privacy' for modification, leaving the agent to infer usage context.

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/billyfranklim1/mcp-evolution'

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