Skip to main content
Glama
chill-lichen

meetergo-mcp

by chill-lichen

create_routing_form

Create a multi-step routing form with branching logic to qualify leads and route them to appropriate meetings, pages, or actions based on conditions.

Instructions

Create a routing form / multi-step funnel with branching logic.

form is the full body. Key fields: name (str), structureType ("FORM_ONLY" | "FUNNEL_WITH_FORM" | "FUNNEL_ONLY"), showProgressBar (bool), funnelSteps: [{ dataFields: [{ dataField: {label, fieldType, options,...} }] }], fields: [{ dataFieldId, order }] (reference existing data fields), qualifiers: [ routing rules ].

A qualifier routes the visitor based on conditions: { "routingAction": "eventRedirect", "meetingTypeId": "...", "expression": {"operator":"and","operands":[ {"operator":"equals","target":"attendeeOther", "customTarget":"Company Size","value":"enterprise"}]} } routingAction ∈ eventRedirect | customPage | externalRedirect | contactForm | requestCallback | instantCall | formRedirect. Include one qualifier with "isFallback": true as the default. Field types include text/email/phone/select/ radio/checkbox/file/signature/pdf-template/currency/rating and more.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
formYes
Behavior4/5

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

No annotations are provided, so the description carries full burden. It details the structure of the form object and qualifier logic but does not disclose side effects, permissions required, or whether the operation is reversible.

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?

The description is well-structured with bullet points and a code example, but it is somewhat lengthy. The main purpose is front-loaded, and every sentence adds value.

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?

Given only one parameter (complex object), no output schema, and no annotations, the description is fairly complete in explaining the input structure. However, it does not specify return values or constraints.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema has 0% coverage for the single 'form' parameter, but the description compensates by providing a detailed breakdown of key fields, types, and examples for qualifiers, adding significant meaning beyond the schema.

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 creates a routing form/multi-step funnel with branching logic. This distinguishes it from sibling tools like get_routing_form, update_routing_form, and delete_routing_form.

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 explains the tool's function but does not provide explicit guidance on when to use it versus alternatives. It lacks context on prerequisites or scenarios where other tools might be more appropriate.

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/chill-lichen/meetergo-mcp'

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