Fine Structure

Create Whatsapp Trigger

create_whatsapp_trigger

Save a WhatsApp trigger for record-created events. It is saved switched off and messages no one. Switching it on is done by the owner on the app's Automations screen in Fine Structure.

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": {
      "app_id": "<app_id>",
      "page_name": "<page_name>",
      "entity_name": "<entity_name>",
      "phone_field": "<phone_field>",
      "message_template": "<message_template>"
    },
    "name": "create_whatsapp_trigger"
  }
}

Input Schema

Name	Required	Description
`name`	No
`app_id`	Yes	The app the trigger belongs to.
`flow_id`	No	Optional WhatsApp flow the conversation continues in.
`page_name`	Yes	The page whose form creates the record.
`name_field`	No
`entity_name`	Yes	The entity whose new records fire it.
`phone_field`	Yes	The record field holding the customer's WhatsApp number.
`whatsapp_bot_id`	No	The WhatsApp number that sends, from get_whatsapp_trigger_options.
`message_template`	Yes	The message; {{ field_name }} inserts a record field.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 6, 2026

TDQS

A4.1/5.0

Behavior5/5

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

Annotations only declare readOnlyHint=false, destructiveHint=false, idempotentHint=false and openWorldHint=false. The description adds the genuinely non-obvious behavior: the saved trigger is switched off by default, sends nothing until enabled, and enabling is an owner-only UI action outside this tool. That is exactly the kind of context annotations cannot convey.

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?

Two short sentences, no redundancy, with the disabled-by-default constraint front-loaded before the follow-up activation detail. Every clause carries actionable information.

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?

For a 9-parameter mutation with no output schema, the description covers the critical lifecycle facts (created disabled, no messages sent, owner enables it later). It omits what the call returns and any prerequisite like the WhatsApp bot/flow existing, leaving a small gap for an agent needing the resulting trigger identifier.

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 78%, so the schema already documents most parameters including the bot id source and the {{ field_name }} template syntax. The description adds no parameter-level meaning beyond implying that entity_name/page_name drive record-created firing, leaving it at the baseline.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("Save a WhatsApp trigger") plus the firing condition ("record-created events"), which is far more than the title restates. It does not explicitly differentiate itself from near-name siblings like create_agent_trigger or update_whatsapp_trigger, so it stops short of a 5.

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?

Gives clear operational context: this tool only persists the trigger in a disabled state, and activation must happen on the app's Automations screen in Fine Structure. It does not say when to prefer update_whatsapp_trigger over creating a new one, nor point to get_whatsapp_trigger_options for the bot id (only the schema does), so it lacks explicit alternatives.

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

All Fine Structure tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?