Skip to main content
Glama

get_booking_link

Create a direct booking link for any queue or meeting type, optionally pre-filling lead contact details to streamline scheduling.

Instructions

Generate a direct booking link for a ChiliPiper queue or meeting type.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queue_slugYesQueue or booking page slug
emailNoPre-fill lead email
first_nameNoPre-fill lead first name
last_nameNoPre-fill lead last name

Implementation Reference

  • index.js:182-205 (registration)
    Tool registration for 'get_booking_link' via server.tool() with name, description, and Zod schema.
    server.tool(
      "get_booking_link",
      "Generate a direct booking link for a ChiliPiper queue or meeting type.",
      {
        queue_slug: z.string().describe("Queue or booking page slug"),
        email: z.string().optional().describe("Pre-fill lead email"),
        first_name: z.string().optional().describe("Pre-fill lead first name"),
        last_name: z.string().optional().describe("Pre-fill lead last name"),
      },
      async ({ queue_slug, email, first_name, last_name }) => {
        const domain = DOMAIN || "your-domain";
        const params = new URLSearchParams();
        if (email) params.set("email", email);
        if (first_name) params.set("firstName", first_name);
        if (last_name) params.set("lastName", last_name);
    
        const qs = params.toString();
        const link = `https://calendar.chilipiper.com/${domain}/${queue_slug}${qs ? "?" + qs : ""}`;
    
        return {
          content: [{ type: "text", text: `Booking link: ${link}` }],
        };
      }
    );
  • Handler function that constructs a ChiliPiper booking link from queue_slug and optional lead fields (email, first_name, last_name).
    async ({ queue_slug, email, first_name, last_name }) => {
      const domain = DOMAIN || "your-domain";
      const params = new URLSearchParams();
      if (email) params.set("email", email);
      if (first_name) params.set("firstName", first_name);
      if (last_name) params.set("lastName", last_name);
    
      const qs = params.toString();
      const link = `https://calendar.chilipiper.com/${domain}/${queue_slug}${qs ? "?" + qs : ""}`;
    
      return {
        content: [{ type: "text", text: `Booking link: ${link}` }],
      };
    }
  • Zod schema defining input parameters: queue_slug (required string), email, first_name, last_name (optional strings).
    {
      queue_slug: z.string().describe("Queue or booking page slug"),
      email: z.string().optional().describe("Pre-fill lead email"),
      first_name: z.string().optional().describe("Pre-fill lead first name"),
      last_name: z.string().optional().describe("Pre-fill lead last name"),
    },
Behavior2/5

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

No annotations provided, and the description does not disclose whether the operation has side effects, requires authentication, or any other behavioral traits. The term 'generate' implies a read-like operation but is not explicit.

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?

Single sentence of 12 words that is front-loaded with the action and resource. No unnecessary words.

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 tool has no output schema, but the description does not explain what the link looks like or its format. It covers the purpose adequately but could provide more context about the return value.

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 has 100% coverage; each parameter has a basic description. The tool description does not add additional meaning beyond the schema, which is acceptable for baseline scoring.

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 uses a specific verb 'Generate' and clearly identifies the resource 'direct booking link for a ChiliPiper queue or meeting type'. It distinguishes from sibling tools that cover configuration and routing.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives like route_concierge or route_lead. No context for appropriate usage or exclusions.

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/hyypeman/chilipiper-mcp'

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