Skip to main content
Glama

Which receptionists write to a business tool

integrations
Read-onlyIdempotent

For Clio, MyCase, Lawmatics, HubSpot, GoHighLevel, Google Calendar, Calendly, Jobber, ServiceTitan, Housecall Pro or Towbook: which AI and virtual receptionists document a built-in integration, which connect through Zapier, and the page that shows it. "Not documented" means neither the vendor's pages nor the tool's directory show it; it is not a guess. Source: ReceptionistPrices.com, prices checked November 17, 2026, https://www.receptionistprices.com/integrations/

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": {
      "tool": "<tool>"
    },
    "name": "integrations"
  }
}

Input Schema

NameRequiredDescriptionDefault
toolYesThe business tool

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive, closed-world behavior, so the description only needs to add context. It does: it defines what 'Not documented' means (absent from both vendor pages and the tool's directory, not a guess) and cites the source and check date, which tells the agent how much to trust the answer.

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?

Two sentences, front-loaded with the scope clause before the explanation of what is returned. The long vendor list is somewhat bulky but mirrors the enum and is not padding; the source/date metadata is compact.

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 one-parameter, read-only lookup with full schema coverage and no output schema, the description covers what is returned (built-in vs Zapier vs undocumented, plus page URL), the data source, and the freshness date. Only a hint about result ordering or completeness of the receptionist list is absent.

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 100% with a single enumerated parameter already labeled 'The business tool', so the schema carries the meaning. The description restates the enum values in prose but adds no new semantics such as case sensitivity or behavior for unsupported values.

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?

States a precise question the tool answers: which AI/virtual receptionists document a built-in integration for a named business tool, which connect via Zapier, and the page showing it. The verb+resource is unambiguous and cannot be confused with the pricing- and vendor-oriented siblings.

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?

Usage is implied by the scoping clause 'For Clio, MyCase, ... :' which shows the tool is queried one business tool at a time, and the 'Not documented' note sets expectations for negative results. There is no explicit when-to-use/when-not guidance or reference to alternatives such as get_vendor_pricing.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources