Skip to main content
Glama
billyfranklim1

mcp-evolution

Send Location

send_location

Send a location pin to a WhatsApp contact or group by providing coordinates, name, and address. Ideal for sharing precise locations in chats.

Instructions

Send a location pin message via the pinned WhatsApp instance.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
numberYesRecipient JID or phone number (e.g. 5511999999999 or group@g.us)
latitudeYesLatitude in decimal degrees
longitudeYesLongitude in decimal degrees
nameNoLocation name/title
addressNoLocation address

Implementation Reference

  • The registerSendLocation function that registers the 'send_location' tool handler. It builds a payload with number, latitude, longitude, and optional name/address, then POSTs to /message/sendLocation/{instanceName}. Errors are handled with McpError.
    export function registerSendLocation(server: McpServer, client: EvolutionClient): void {
      server.registerTool(
        "send_location",
        {
          title: "Send Location",
          description: "Send a location pin message via the pinned WhatsApp instance.",
          inputSchema: schema,
        },
        async (args) => {
          try {
            const payload: Record<string, unknown> = {
              number: args.number,
              latitude: args.latitude,
              longitude: args.longitude,
            };
            if (args.name) payload["name"] = args.name;
            if (args.address) payload["address"] = args.address;
            const data = await client.post(`/message/sendLocation/${client.instanceName}`, payload);
            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 send_location: number (PhoneOrJidSchema), latitude (number), longitude (number), and optional name and address strings.
    const schema = {
      number: PhoneOrJidSchema,
      latitude: z.number().describe("Latitude in decimal degrees"),
      longitude: z.number().describe("Longitude in decimal degrees"),
      name: z.string().optional().describe("Location name/title"),
      address: z.string().optional().describe("Location address"),
    };
  • Import of registerSendLocation from ./send-location.js
    import { registerSendLocation } from "./send-location.js";
    import { registerSendContact } from "./send-contact.js";
    import { registerSendReaction } from "./send-reaction.js";
    import { registerSendPoll } from "./send-poll.js";
    import { registerSendList } from "./send-list.js";
    import { registerSendButton } from "./send-button.js";
  • Registration call: registerSendLocation(server, client) invoked inside registerAllTools.
    registerSendLocation(server, client);
  • PhoneOrJidSchema helper: a zod string schema for recipient JID or phone number, used by the send_location schema.
    export const PhoneOrJidSchema = z
      .string()
      .min(1)
      .describe("Recipient JID or phone number (e.g. 5511999999999 or group@g.us)");
Behavior3/5

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

With no annotations, the description carries full burden. It briefly mentions the use of a pinned instance, but does not disclose behavior like side effects, error handling, or permission requirements. Acceptable but not rich.

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, concise sentence that efficiently communicates the tool's purpose. No filler or redundancy.

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?

For a tool of this complexity (5 params, no output schema), the description provides minimal context. It does not mention return values, failure modes, or integration details. Adequate but incomplete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 100% description coverage for all 5 parameters, so the schema already documents each parameter adequately. The description does not add extra meaning beyond the schema, warranting a baseline score of 3.

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 action (send), resource (location pin message), and context (via pinned WhatsApp instance). It distinguishes effectively from siblings that send other message types like audio, media, text, etc.

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 provides no guidance on when to use this tool versus alternatives. It does not mention prerequisites, exclusions, or typical use cases. For a simple tool, minimal guidance is acceptable but not exemplary.

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