Skip to main content
Glama
billyfranklim1

mcp-evolution

Get Settings

get_settings

Retrieve the current settings for your pinned WhatsApp instance.

Instructions

Get the current settings of the pinned WhatsApp instance.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The registerGetSettings function registers the 'get_settings' tool on the MCP server. It calls the Evolution API GET /settings/find/:instanceName and returns the response as JSON.
    export function registerGetSettings(server: McpServer, client: EvolutionClient): void {
      server.registerTool(
        "get_settings",
        {
          title: "Get Settings",
          description: "Get the current settings of the pinned WhatsApp instance.",
          inputSchema: {},
        },
        async () => {
          try {
            const data = await client.get(`/settings/find/${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;
          }
        }
      );
    }
  • Input schema for the 'get_settings' tool: an empty object (no parameters), with title 'Get Settings' and description 'Get the current settings of the pinned WhatsApp instance.'
    {
      title: "Get Settings",
      description: "Get the current settings of the pinned WhatsApp instance.",
      inputSchema: {},
  • Registration call: registerGetSettings(server, client) invoked in the tools index.
    registerGetSettings(server, client);
  • Import statement for registerGetSettings from './get-settings.js'.
    import { registerGetSettings } from "./get-settings.js";
Behavior4/5

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

The description discloses that the tool reads settings, a non-destructive operation. With no annotations provided, the description carries the full burden, and it adequately conveys the behavior for a simple getter.

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, front-loaded sentence with no wasted words. It is appropriately sized for the tool's simplicity.

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 no output schema, the description is sufficient for a parameterless getter. However, it could be improved by indicating what the settings include or the return format.

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 input schema has no parameters, so schema coverage is 100%. The description adds meaning by specifying 'pinned WhatsApp instance', clarifying the scope of the settings.

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 'Get' and the resource 'current settings of the pinned WhatsApp instance', distinguishing it from sibling tools like set_settings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies that this tool is for reading settings, but does not explicitly state when to use it versus alternatives like set_settings. The context is clear for a simple getter, but lacks explicit guidance.

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