Skip to main content
Glama

route_concierge

Route a lead through ChiliPiper Concierge to return the booking calendar URL for an inbound router.

Instructions

Route a lead via the ChiliPiper Concierge fire endpoint. Returns the booking calendar URL for an inbound router.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
router_slugYesThe inbound Concierge router URL slug
emailYesLead's email address
first_nameNoLead's first name
last_nameNoLead's last name
companyNoLead's company
phoneNoLead's phone
extra_fieldsNoAdditional fields as key-value pairs

Implementation Reference

  • index.js:126-179 (registration)
    Registration of the 'route_concierge' tool with server.tool(), including its description and schema definition.
    // --- Tool: Route via Concierge fire endpoint ---
    server.tool(
      "route_concierge",
      "Route a lead via the ChiliPiper Concierge fire endpoint. Returns the booking calendar URL for an inbound router.",
      {
        router_slug: z
          .string()
          .describe("The inbound Concierge router URL slug"),
        email: z.string().describe("Lead's email address"),
        first_name: z.string().optional().describe("Lead's first name"),
        last_name: z.string().optional().describe("Lead's last name"),
        company: z.string().optional().describe("Lead's company"),
        phone: z.string().optional().describe("Lead's phone"),
        extra_fields: z
          .record(z.string())
          .optional()
          .describe("Additional fields as key-value pairs"),
      },
      async ({
        router_slug,
        email,
        first_name,
        last_name,
        company,
        phone,
        extra_fields,
      }) => {
        const body = {
          PersonEmail: email,
          ...(first_name && { FirstName: first_name }),
          ...(last_name && { LastName: last_name }),
          ...(company && { Company: company }),
          ...(phone && { Phone: phone }),
          ...(extra_fields || {}),
        };
    
        try {
          const result = await cpFetch(
            `${FIRE_URL}/concierge-router/${router_slug}/rest`,
            {
              method: "POST",
              body: JSON.stringify(body),
            }
          );
          return {
            content: [{ type: "text", text: JSON.stringify(result, null, 2) }],
          };
        } catch (err) {
          return {
            content: [{ type: "text", text: `Error: ${err.message}` }],
          };
        }
      }
    );
  • Zod schema defining input parameters for route_concierge: router_slug, email, first_name, last_name, company, phone, extra_fields.
    {
      router_slug: z
        .string()
        .describe("The inbound Concierge router URL slug"),
      email: z.string().describe("Lead's email address"),
      first_name: z.string().optional().describe("Lead's first name"),
      last_name: z.string().optional().describe("Lead's last name"),
      company: z.string().optional().describe("Lead's company"),
      phone: z.string().optional().describe("Lead's phone"),
      extra_fields: z
        .record(z.string())
        .optional()
        .describe("Additional fields as key-value pairs"),
    },
  • Handler function that POSTs lead data to the ChiliPiper Concierge fire endpoint at FIRE_URL/concierge-router/{router_slug}/rest and returns the booking calendar URL.
    async ({
      router_slug,
      email,
      first_name,
      last_name,
      company,
      phone,
      extra_fields,
    }) => {
      const body = {
        PersonEmail: email,
        ...(first_name && { FirstName: first_name }),
        ...(last_name && { LastName: last_name }),
        ...(company && { Company: company }),
        ...(phone && { Phone: phone }),
        ...(extra_fields || {}),
      };
    
      try {
        const result = await cpFetch(
          `${FIRE_URL}/concierge-router/${router_slug}/rest`,
          {
            method: "POST",
            body: JSON.stringify(body),
          }
        );
        return {
          content: [{ type: "text", text: JSON.stringify(result, null, 2) }],
        };
      } catch (err) {
        return {
          content: [{ type: "text", text: `Error: ${err.message}` }],
        };
      }
    }
  • The cpFetch helper used by the handler to make authenticated API calls to ChiliPiper.
    async function cpFetch(url, options = {}) {
      const headers = {
        "Content-Type": "application/json",
        ...(API_KEY ? { "x-api-token": API_KEY } : {}),
        ...options.headers,
      };
      const res = await fetch(url, { ...options, headers });
      const text = await res.text();
      if (!res.ok) {
        throw new Error(`ChiliPiper API ${res.status}: ${text}`);
      }
      try {
        return JSON.parse(text);
      } catch {
        return text;
      }
    }
Behavior2/5

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

With no annotations, the description fully carries the burden. It only mentions the return value (booking calendar URL) but does not disclose side effects, authorization needs, or whether the action is destructive. The agent cannot assess impact.

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 concise at two sentences, front-loading the core action and output. However, the first sentence could be slightly tighter.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 7 parameters, no output schema, and no annotations, the description omits many details: error handling, side effects, prerequisites (e.g., valid router_slug), and what happens to the lead. Incomplete for safe invocation.

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?

The input schema covers all 7 parameters with descriptions (100% coverage), so the description adds no additional meaning. Baseline of 3 is appropriate.

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?

The description clearly states the tool routes a lead and returns a booking calendar URL, with specific reference to ChiliPiper Concierge. However, it does not differentiate from the sibling tool 'route_lead', which may have overlapping functionality.

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 is provided on when to use this tool versus alternatives like 'route_lead' or 'get_booking_link'. The description lacks context for appropriate scenarios.

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