ErzyCall

save_whatsapp_tool

Add or edit non-secret configuration for a WhatsApp HTTP, remote MCP, platform or connected-app tool after confirming the exact change. Pass id to edit and complete configuration; omit url to preserve an existing endpoint. Input schema must describe an object. This customer MCP schema rejects credentials; manage authentication headers in dashboard settings or through the REST API. Creating a tool does not enable it; assign IDs using update_whatsapp_agent updates.externalToolIds. Reuse the same idempotencyKey on retries. Requires whatsapp_agents:write.

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": {
      "tool": "<tool>",
      "confirmed": "<confirmed>",
      "idempotencyKey": "<idempotencyKey>"
    },
    "name": "save_whatsapp_tool"
  }
}

Input Schema

Name	Required	Description
`id`	No
`tool`	Yes
`confirmed`	Yes	Must be true only after the user explicitly confirms this exact operation
`idempotencyKey`	Yes	A unique identifier generated once for this intended write. Reuse exactly when retrying.

Output Schema

Name	Required	Description	Default
`data`	No
`success`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 17, 2026

addedInput schema / properties / tool / properties / httpParameters

Added value: +{
+  "additionalProperties": {
+    "additionalProperties": false,
+    "properties": {
+      "arrayFormat": {
+        "enum": [
+          "repeat",
+          "brackets",
+          "json"
+        ],
+        "type": "string"
+      },
+      "in": {
+        "enum": [
+          "path",
+          "query",
+          "body"
+        ],
+        "type": "string"
+      },
+      "name": {
+        "minLength": 1,
+        "type": "string"
+      }
+    },
+    "required": [
+      "in"
+    ],
+    "type": "object"
+  },
+  "propertyNames": {
+    "minLength": 1,
+    "type": "string"
+  },
+  "type": "object"
+}

AddedOct 7, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations only declare the write/safety profile (readOnlyHint=false, destructiveHint=false, openWorldHint=false). The description adds substantial non-obvious behavior: credentials are rejected by this schema, auth headers live in dashboard/REST, creating a tool does not enable it, and idempotencyKey must be reused verbatim on retries. This is exactly the extra context the bar asks for.

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 and most sentences earn their place (edit semantics, credential rejection, enablement, idempotency, auth scope). It is densely packed and slightly long, with the schema-shape and credential notes competing for attention, but no sentence is pure filler.

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?

For a 4-parameter mutation with nested objects, the description covers the mutation model, partial-edit behavior, auth scope (whatsapp_agents:write), and retry semantics. An output schema exists, so return values legitimately need no explanation.

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?

With 50% schema description coverage, the description compensates well by explaining id (edit mode), url omission as endpoint preservation, confirmed, and idempotencyKey reuse. It does not clarify the many nested tool fields (kind, transport, httpParameters, platformToolId, requiresConfirmation), so some of the coverage gap remains.

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 pair (add or edit) and a well-scoped resource (non-secret configuration for a WhatsApp HTTP/MCP/platform/connected-app tool). The scope question 'non-secret configuration' immediately distinguishes it from delete_whatsapp_tool, list_whatsapp_tools, and update_whatsapp_agent.

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

Usage Guidelines5/5

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

Explicit when-to-use rules: pass id to edit, omit url to preserve an existing endpoint, confirm the exact change first, and use update_whatsapp_agent to assign IDs after creation. It also routes the agent elsewhere for credential management. Nothing about selection is left to inference.

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

All ErzyCall tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?