Skip to main content
Glama
jppeiro90

MCP-WHATSAPP-EVO

by jppeiro90

fetch_business_profile

Retrieve the WhatsApp Business profile of a phone number using an Evolution API instance. Provide instance name and number with country code to get profile details.

Instructions

Fetch the WhatsApp Business profile of a number.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
numberYesPhone number with country code
instanceNameYesName of the Evolution API instance
Behavior1/5

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

No annotations provided; description only states action without disclosing side effects, permissions, error cases, or read-only nature.

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?

Single sentence is concise and front-loaded, but could benefit from slightly more context without becoming verbose.

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?

Simple tool, schema covers params, but missing output format and usage context; adequate but with gaps.

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?

Schema has 100% description coverage for both parameters; description adds no additional meaning beyond schema descriptions.

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?

Description clearly states verb 'Fetch' and resource 'WhatsApp Business profile of a number', distinguishing it from sibling tools like fetch_profile and fetch_privacy_settings.

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 on when to use this tool vs alternatives such as fetch_profile, nor prerequisites or when not to use.

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/jppeiro90/MCP-WHATSAPP-EVO'

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