meetergo-mcp

send_routing_form

Send a routing form to a recipient via email, SMS, or generate a one-time link. Returns public URL and status.

Instructions

Send a routing form to a recipient (one-time link). Returns {publicUrl, status}.

Args: form_id: Form to send. recipient_name: Recipient display name. email: Required if delivery_method="email". phone: Required if delivery_method="sms". message: Optional cover message. delivery_method: "email" | "sms" | "link" (link = generate URL only).

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": {
      "form_id": "<form_id>",
      "recipient_name": "<recipient_name>"
    },
    "name": "send_routing_form"
  }
}

Input Schema

Name	Required	Default
`email`	No
`phone`	No
`form_id`	Yes
`message`	No
`recipient_name`	Yes
`delivery_method`	No	email

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Jul 8, 2026

TDQS

A3.7/5.0

Behavior2/5

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

With no annotations provided, the description carries full responsibility for behavioral disclosure. It mentions the return format and that the link is one-time, but does not disclose side effects (e.g., whether it creates a record), idempotency, or error behavior. This leaves significant gaps for a tool that sends communications.

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 extremely concise: a single sentence stating the purpose and return, followed by a brief, well-structured parameter list. Every sentence adds value, and the most important information is front-loaded.

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?

The description adequately covers parameter usage and return values, but given the lack of annotations and output schema, it omits important context like error states, prerequisites (e.g., form must exist), and behavioral nuances (e.g., sending costs). It is sufficient for basic use but not fully comprehensive.

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?

Since schema description coverage is 0%, the description adds critical context: it explains conditional requirements for email/phone based on delivery_method, clarifies that message is optional, and enumerates delivery_method options. This goes well beyond the schema which only provides types and defaults.

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 tool sends a routing form as a one-time link and returns {publicUrl, status}. This distinguishes it from sibling tools like create_routing_form or delete_routing_form, which perform different operations.

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 conditional requirements for email/phone based on delivery_method, but does not explicitly state when to use this tool versus alternatives. It implies usage through parameter descriptions but lacks explicit guidance on scenarios or exclusions.

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