Skip to main content
Glama

get_whatsapp_ai_rules

Read-onlyIdempotent

Read the WhatsApp "AI rules" of a Convocore agent: the rules that decide whether the AI replies to an inbound WhatsApp message (dashboard: Channels → WhatsApp → AI rules). Returns inboundEngagement (null when never configured — then the AI replies to everything except what the legacy per-number guards block), the defaults, every WhatsApp number assigned to the agent with its phoneId and AI settings (aiPaused, newContactsOnly, coexistenceSettings), and warnings for configurations that keep the AI silent. Meta credentials are never returned. Call this before update_whatsapp_ai_rules / update_whatsapp_number_settings.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "agentId": "<agentId>"
    },
    "name": "get_whatsapp_ai_rules"
  }
}

Input Schema

NameRequiredDescriptionDefault
agentIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare the safe read-only/idempotent profile, and the description adds substantive behavior: inboundEngagement is null when never configured (with the resulting reply-everything fallback), the response includes per-number AI settings and warnings for configs that silence the AI, and Meta credentials are never returned. These are non-obvious semantics an agent could not infer from structured fields.

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?

Purpose is front-loaded in the first clause, and the return-shape detail and the 'call this before' rule are ordered sensibly at the end. It is dense but nearly every clause carries information; the parenthetical dashboard path is the only mild extra.

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

Completeness5/5

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

With no output schema, the description carries the return-shape burden and does so thoroughly — enumerating the key fields, the null case, and warnings. Combined with the stated mutation prerequisite, an agent has everything needed to call it and interpret the result.

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 coverage is 0% and the single agentId parameter has no schema description; the description only implies the agent identity via 'of a Convocore agent.' For one obvious identifier this is adequate, but it adds no format or source guidance for agentId.

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?

States a specific verb and resource — reading an agent's WhatsApp 'AI rules' — and immediately defines what those rules govern (whether the AI replies to an inbound message), plus the dashboard location. An agent can distinguish this from update_whatsapp_ai_rules and whatsapp_numbers_read without opening the schema.

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

Usage Guidelines4/5

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

Ends with an explicit prerequisite: 'Call this before update_whatsapp_ai_rules / update_whatsapp_number_settings,' which is a concrete sequencing rule. It does not address when to prefer this over whatsapp_numbers_read, which returns overlapping number data, so the routing guidance is incomplete rather than absent.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources