Skip to main content
Glama

Book Enhanced Intelligence LLC

by com.enhancedint
OverviewDiscussionsAdmin

Server Details

Book with Enhanced Intelligence LLC: services, prices and open times. No key needed.

If you are the author of this connector, you can claim ownership by verifying the domain or GitHub account it belongs to. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Uptime
99.9% over 20 days
Last Tested
Transport
Streamable HTTP · MCP 2025-06-18
URL

TDQS

A4.1/5.0

Scored across 6 tools

Disambiguation5/5

Each tool has a clearly distinct purpose: discovering business info, finding availability, validating an address, booking, checking a booking, and cancelling. The names and descriptions make it easy to select the right tool without overlap.

Naming Consistency4/5

Five tools follow a clear verb_noun pattern (cancel_booking, check_address, find_times, get_booking, get_business). The main booking action is just 'book' rather than 'create_booking' or 'book_time', which is a minor deviation but still readable.

Tool Count5/5

Six tools are well-scoped for a booking workflow. Each tool covers a necessary step—discovery, availability, address validation, booking, status check, and cancellation—without unnecessary bloat.

Completeness4/5

The core booking lifecycle is covered: business discovery, time finding, address checking, booking creation, status retrieval, and cancellation. Rescheduling or updating an existing booking is not directly supported, but cancellation plus rebooking provides a reasonable workaround.

Available Tools

6 tools
bookBookA
Idempotent
Inspect

Book one of the open times for the customer. The business then either confirms it at once or receives it as a request it approves (or, for a business that takes its bookings by email, confirms with the customer itself); the answer says which, what happens next, and a manage.token to check or cancel the booking later. The customer is emailed. Confirm the service, the time and the customer's details with the customer before calling it. idempotency_key is required: choose a new random one for each booking (a UUID without hyphens) and send the same one to retry after a timeout, so a retry cannot make a second booking.

NameRequiredDescriptionDefault
tintNoWhat is being booked at a window tint business, in place of `items` (the card says which a business takes): the class of the customer's car, the windows, the film and the shade, each chosen from the card's `tint` section. The business prices and times it; a shade never changes the price. Choosing the front two windows and the rear sides books the full vehicle, at its price.
agentYesWho is booking, so the business sees that an agent made the booking and which one.
itemsNoWhat is being booked. May be left out only when the business offers exactly one service (a consulting business's one kind of call). A window tint business takes `tint` instead, never items.
startYesA start time from `times`, ISO 8601 with an offset, on a whole minute: seconds, when written, are 00 ("2026-10-12T10:00:00-07:00" or "2026-10-12T17:00Z"). It is checked again, and refused with `time_not_open` if it is no longer open.
answersNoAnswers to the questions the card lists under booking.answers, by their `id`. Each question there says its exact format and shows an example that passes: a select takes exactly one of its option strings, copied character for character; a multiselect takes a list of its option strings (at most its `maxSelections`, each once); a text, a long text, an email, a phone number and a web address each have a stated length limit; a select with `allowOther` takes "Other" with the customer's own words under `<id>_other`; and a question with a `none` phrase takes exactly that phrase when there is no answer. A business that comes to the customer (a mobile detailer or tint shop) asks for `address`: check it first (POST /agent/address, the MCP tool check_address) and send the `address` that answers. The address is checked again here, and refused with `address_invalid`, `address_unconfirmed` (with the corrected address) or `outside_service_area`. When Google could not confirm it or corrected it, and the customer says theirs is right as they gave it, send theirs with `address_confirmed: true`: it is filed as given, for the business to check (never past `outside_service_area`). Leave out when the card lists none.
customerYesThe person the booking is for. They receive the confirmation email.
idempotency_keyYesRequired. A key you choose, new for each booking: 32 to 255 letters, digits, dashes or underscores, and RANDOM, never a counter, a word or a pattern (a UUID without hyphens is right; a key with fewer than 8 distinct characters is refused). Calling book again with the same key and customer email answers the first booking again, with the same manage token, instead of making a second one: use it to retry safely after a timeout.

TDQS

A4.5/5.0
Behavior5/5

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

Beyond annotations, it explains the possible booking outcomes (instant confirmation, approval request, email-based confirmation), that the customer is emailed, that the response includes a manage token, and how idempotency retries avoid duplicate bookings. This is exactly the behavioral context an agent needs for a mutation tool.

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 front-loaded with purpose, then outcome, then required pre-call confirmation, then the idempotency rule. Every sentence carries operational meaning, with no filler.

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

Completeness5/5

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

For a complex booking tool with nested objects and no output schema, the description supplies the missing return/outcome context (confirmation vs. request vs. email, manage token) and the critical retry semantics. The schema handles parameter details, so nothing essential is left ambiguous.

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 description coverage is 100%, so the schema already documents parameters in depth. The description restates the idempotency_key requirement and format but adds little parameter meaning beyond what the schema provides, making 3 the appropriate baseline.

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 opens with a specific verb and resource: 'Book one of the open times for the customer.' That makes clear it creates a booking, distinct from sibling tools like find_times, get_booking, and cancel_booking. The following sentences further pin down the booking flow and outcome.

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

Usage Guidelines4/5

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

It gives clear context and prerequisites: book an open time, confirm service/time/customer details with the customer first, and use idempotency keys only for retries. It does not explicitly name find_times as the way to obtain open times, nor does it state when not to call book, so it falls short of full when/when-not guidance.

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

cancel_bookingCancel a bookingA
DestructiveIdempotent
Inspect

Cancel a booking made through this door: withdraws a request still waiting, or cancels a booking the business confirmed at once. A booking the business has approved must be changed with the business directly (the answer says how). Ask the customer first.

NameRequiredDescriptionDefault
tokenYesThe booking's `manage.token`, from book.
referenceYesThe booking's `reference`, from book.

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, openWorldHint=true and readOnlyHint=false, so the safety profile is covered. The description adds genuine value beyond them by disclosing state-dependent behavior and the fact that approved bookings are out of scope here and the response explains the alternative path. It does not detail auth requirements or what the returned payload looks like.

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?

Three tight sentences with the core action front-loaded, followed by the exclusion and a short caution. Every sentence carries weight, though the standalone 'Ask the customer first' is slightly abrupt and the state enumeration could be marginally more 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 destructive, open-world two-parameter mutation tool with no output schema, the description covers the essentials: what it cancels, the state conditions, the exclusion, and that the response tells the caller how to proceed for approved bookings. It is close to complete, missing only richer detail on the response payload or auth expectations.

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 description coverage is 100%, so the schema already documents both `token` and `reference` as coming from book. The description adds no syntax or format detail beyond that, so the baseline 3 applies; the 'made through this door' phrasing is contextual rather than parameter-specific.

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 specific verb (cancel) and resource (booking) and goes further by splitting the action into two distinct states: withdrawing a still-waiting request versus cancelling a business-confirmed booking. An agent immediately understands what is being cancelled and under which conditions, with no overlap among the read-oriented siblings (book, find_times, get_booking, get_business).

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

Usage Guidelines5/5

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

Gives explicit when-to-use conditions (pending request, or a booking the business confirmed at once) and an explicit when-not-to-use exclusion: a business-approved booking must be changed with the business directly. It also adds a procedural prerequisite, 'Ask the customer first', leaving little to inference.

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

check_addressCheck an addressA
Read-onlyIdempotent
Inspect

For a business that comes to the customer: check the service address before booking. Send it as one line, as fields, or as a place_id saved from an earlier check. The answer says whether Google confirmed it (verdict), the address to book with (send it as answers.address), its place_id (save both for this customer; next time send the place_id, with the apartment or unit as extended_address if there is one), and whether it is inside the area the business serves. Book when bookable is true; when the verdict is confirm, read the corrected address to the customer first. next says what to do otherwise.

NameRequiredDescriptionDefault
addressYes

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover readOnly/idempotent/openWorld, but the description adds real context: the external Google confirmation step, the shape of the response (verdict, answers.address, place_id, bookable, next), and the persistence recommendation to save place_id per customer and pass extended_address for units. It stops short of enumerating verdict or `next` values, and mentions no rate limits or auth needs.

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?

Front-loaded with the purpose, and every sentence carries actionable information about inputs and outcomes. The second sentence is a dense, heavily parenthesized run-on that takes effort to parse, which costs it the top mark.

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?

With no output schema, the description carries the burden of describing returns and it names the key fields (verdict, answers.address, place_id, bookable, next) and how to act on two of them. It never defines the possible verdict or `next` values, so an agent still has to infer some response semantics.

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?

Top-level property description coverage is reported as 0%, so the description must compensate, and it does: it tells the agent the input can be one line, a field object, or a saved place_id, and that extended_address carries the unit. The rich oneOf schema already documents the three spellings, so the description mostly reinforces workflow rather than adding new syntax.

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 specific verb and resource ('check the service address before booking') plus the scope that distinguishes it from siblings: a business that comes to the customer. An agent can tell this apart from book/find_times/get_booking without opening the schema.

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

Usage Guidelines4/5

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

Gives strong conditional routing downstream ('Book when `bookable` is true', 'when the verdict is `confirm`, read the corrected address to the customer first', '`next` says what to do otherwise') and instructs reusing a saved place_id on the next call. It does not state when *not* to call check_address or name a sibling as an explicit alternative, so it falls just short of a 5.

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

find_timesFind open timesA
Read-onlyIdempotent
Inspect

Find the start times that are open for what is being booked, between two dates (at most 14 days). Pass windows (the customer's free time from their calendar) to get only the starts that fit both calendars. Returns ISO 8601 times with offsets. Only open times are ever shown.

NameRequiredDescriptionDefault
toYesLast day, YYYY-MM-DD. At most 14 days from `from`, counting both, and at most 60 days from today.
fromYesFirst day, YYYY-MM-DD, in the business's time zone (the card names it). Not in the past.
tintNoWhat is being booked at a window tint business, in place of `items` (the card says which a business takes): the class of the customer's car, the windows, the film and the shade, each chosen from the card's `tint` section. The business prices and times it; a shade never changes the price. Choosing the front two windows and the rear sides books the full vehicle, at its price.
itemsNoWhat is being booked. May be left out only when the business offers exactly one service (a consulting business's one kind of call). A window tint business takes `tint` instead, never items.
windowsNoThe customer's free time, as intervals with offsets. When given, only starts whose whole job or meeting fits inside one window come back. Leave out to see every open start.

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive), and the description adds real value: a 14-day cap, ISO 8601-with-offset return format, and the guarantee that only open times are shown. It doesn't discuss pagination or response size, which is a minor gap.

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?

Three sentences, each earning its place: purpose first, then the windowing condition, then the return format. Nothing redundant.

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

Completeness5/5

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

With no output schema, the description steps in to describe return values (ISO 8601 times with offsets, open only). Combined with the rich input schema and annotations, an agent has everything needed to call it correctly.

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 description coverage is 100%, so the parameters are already well documented. The description reinforces the meaning of `windows` (only starts fitting both calendars), but adds little beyond what the schema states.

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 specific verb and resource ('find the start times that are open') plus the scope of what is being booked and the date range. An agent can distinguish it from siblings like 'book' or 'get_booking' immediately.

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

Usage Guidelines4/5

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

The description frames this as the lookup that precedes booking and explains when to pass `windows` (to intersect with the customer's calendar) versus leaving it out. It stops short of explicitly naming the sibling to call afterward, but the context is clear.

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

get_bookingCheck a bookingA
Read-onlyIdempotent
Inspect

Check a booking made through this door: whether it is requested, confirmed, declined or cancelled, and whether it can still be cancelled here.

NameRequiredDescriptionDefault
tokenYesThe booking's `manage.token`, from book.
referenceYesThe booking's `reference`, from book.

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description goes beyond them by disclosing the status values returned and that it evaluates remaining cancellability, which is genuinely useful behavioral context.

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?

A single front-loaded sentence with no filler. The phrase 'made through this door' is slightly idiosyncratic and could read as jargon, which keeps it from a 5.

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

Completeness5/5

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

There is no output schema, so the description carries the return-value burden and does so by naming the possible booking states and the cancellability result. For a two-parameter read tool with full annotation coverage, nothing essential is missing.

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% and both parameters are described in the schema as coming from book (`manage.token` and `reference`). The description adds no format, syntax, or lookup detail, so the baseline of 3 for full schema coverage applies.

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?

States a specific verb (check) and resource (a booking), and enumerates the states it reports (requested, confirmed, declined, cancelled) plus whether cancellation is still possible here. This sets it apart from the write-oriented cancel_booking, though no sibling is named explicitly.

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 rather than stated: the phrase 'whether it can still be cancelled here' hints this is the read step preceding cancel_booking, but there is no explicit when-to-use, when-not-to-use, or named alternative.

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

get_businessGet the businessA
Read-onlyIdempotent
Inspect

Read the business card: what it is, where the work happens, its hours and time zone, its services with prices and lengths, what a booking needs (the customer's details and the questions to answer), whether a booking is confirmed at once or sent as a request, the limits and the cancel rule. Call it first.

NameRequiredDescriptionDefault

No parameters

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false and destructiveHint=false, so the safety profile is fully covered by structured data. The description adds the ordering requirement ('call it first') but discloses nothing about authorization, rate limits, or data freshness, which is what would push this above baseline.

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?

A single sentence, with the purpose front-loaded and the actionable directive ('Call it first') at the end. The mid-sentence enumeration is dense but each item maps to real returned data, so nothing is padding.

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

Completeness5/5

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

There is no output schema, so the description carries the burden of telling the agent what comes back, and it does: identity, location, hours, time zone, services/prices/durations, required booking inputs, confirmation semantics, limits, and cancellation policy. That inventory is exactly what an agent needs before calling book or find_times.

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?

The tool takes zero parameters and the schema has additionalProperties=false, so there is nothing to disambiguate and no parameter syntax the agent could get wrong. Baseline 4 for a parameterless tool.

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 concrete verb ('Read') and resource ('the business card') and then enumerates the exact scope: identity, location, hours, time zone, services with prices and lengths, booking requirements, confirmation mode, limits and cancel rule. An agent can tell this apart from siblings like book or find_times purely from the description.

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

Usage Guidelines4/5

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

'Call it first' gives explicit sequencing guidance and marks this as the entry point relative to book/get_booking. It does not name an alternative or state when *not* to call it, so it stops short of a full when/when-not/alternatives treatment.

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

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 2 tool updates
    • Changedbook1 field changed
      • changedInput schema / examples
        Previous value: -[
-  {
-    "agent": {
-      "name": "Your agent name"
-    },
-    "answers": {
-      "budget": "Not sure yet",
-      "business_name": "Analytical Engines Ltd",
-      "decider": "I decide with a partner",
-      "industry": "Professional services",
-      "notes": "We lose leads that message after hours.",
-      "pains": [
-        "Slow replies to new leads",
-        "Hours of admin and data entry"
-      ],
-      "team_size": "Just me",
-      "timeline": "In the next three months",
-      "website": "analyticalengines.example"
-    },
-    "customer": {
-      "email": "ada@example.com",
-      "name": "Ada Lovelace",
-      "phone": "(619) 555-0123",
-      "time_zone": "Europe/London"
-    },
-    "idempotency_key": "replace-this-with-a-fresh-random-key-0000",
-    "items": [
-      {
-        "slug": "discovery-call"
-      }
-    ],
-    "start": "2026-10-25T08:00:00-07:00"
-  }
-]New value: +[
+  {
+    "agent": {
+      "name": "Your agent name"
+    },
+    "answers": {
+      "budget": "Not sure yet",
+      "business_name": "Analytical Engines Ltd",
+      "decider": "I decide with a partner",
+      "industry": "Professional services",
+      "notes": "We lose leads that message after hours.",
+      "pains": [
+        "Slow replies to new leads",
+        "Hours of admin and data entry"
+      ],
+      "team_size": "Just me",
+      "timeline": "In the next three months",
+      "website": "analyticalengines.example"
+    },
+    "customer": {
+      "email": "ada@example.com",
+      "name": "Ada Lovelace",
+      "phone": "(619) 555-0123",
+      "time_zone": "Europe/London"
+    },
+    "idempotency_key": "replace-this-with-a-fresh-random-key-0000",
+    "items": [
+      {
+        "slug": "discovery-call"
+      }
+    ],
+    "start": "2026-10-26T08:00:00-07:00"
+  }
+]
    • Changedfind_times1 field changed
      • changedInput schema / examples
        Previous value: -[
-  {
-    "from": "2026-10-25",
-    "items": [
-      {
-        "slug": "discovery-call"
-      }
-    ],
-    "to": "2026-10-31",
-    "windows": [
-      {
-        "end": "2026-10-25T13:00:00-07:00",
-        "start": "2026-10-25T08:00:00-07:00"
-      }
-    ]
-  }
-]New value: +[
+  {
+    "from": "2026-10-26",
+    "items": [
+      {
+        "slug": "discovery-call"
+      }
+    ],
+    "to": "2026-11-01",
+    "windows": [
+      {
+        "end": "2026-10-26T18:00:00-07:00",
+        "start": "2026-10-26T08:00:00-07:00"
+      }
+    ]
+  }
+]
  2. 2 tool updates
    • Changedbook1 field changed
      • changedInput schema / examples
        Previous value: -[
-  {
-    "agent": {
-      "name": "Your agent name"
-    },
-    "answers": {
-      "budget": "Not sure yet",
-      "business_name": "Analytical Engines Ltd",
-      "decider": "I decide with a partner",
-      "industry": "Professional services",
-      "notes": "We lose leads that message after hours.",
-      "pains": [
-        "Slow replies to new leads",
-        "Hours of admin and data entry"
-      ],
-      "team_size": "Just me",
-      "timeline": "In the next three months",
-      "website": "analyticalengines.example"
-    },
-    "customer": {
-      "email": "ada@example.com",
-      "name": "Ada Lovelace",
-      "phone": "(619) 555-0123",
-      "time_zone": "Europe/London"
-    },
-    "idempotency_key": "replace-this-with-a-fresh-random-key-0000",
-    "items": [
-      {
-        "slug": "discovery-call"
-      }
-    ],
-    "start": "2026-10-24T08:00:00-07:00"
-  }
-]New value: +[
+  {
+    "agent": {
+      "name": "Your agent name"
+    },
+    "answers": {
+      "budget": "Not sure yet",
+      "business_name": "Analytical Engines Ltd",
+      "decider": "I decide with a partner",
+      "industry": "Professional services",
+      "notes": "We lose leads that message after hours.",
+      "pains": [
+        "Slow replies to new leads",
+        "Hours of admin and data entry"
+      ],
+      "team_size": "Just me",
+      "timeline": "In the next three months",
+      "website": "analyticalengines.example"
+    },
+    "customer": {
+      "email": "ada@example.com",
+      "name": "Ada Lovelace",
+      "phone": "(619) 555-0123",
+      "time_zone": "Europe/London"
+    },
+    "idempotency_key": "replace-this-with-a-fresh-random-key-0000",
+    "items": [
+      {
+        "slug": "discovery-call"
+      }
+    ],
+    "start": "2026-10-25T08:00:00-07:00"
+  }
+]
    • Changedfind_times1 field changed
      • changedInput schema / examples
        Previous value: -[
-  {
-    "from": "2026-10-24",
-    "items": [
-      {
-        "slug": "discovery-call"
-      }
-    ],
-    "to": "2026-10-30",
-    "windows": [
-      {
-        "end": "2026-10-24T13:00:00-07:00",
-        "start": "2026-10-24T08:00:00-07:00"
-      }
-    ]
-  }
-]New value: +[
+  {
+    "from": "2026-10-25",
+    "items": [
+      {
+        "slug": "discovery-call"
+      }
+    ],
+    "to": "2026-10-31",
+    "windows": [
+      {
+        "end": "2026-10-25T13:00:00-07:00",
+        "start": "2026-10-25T08:00:00-07:00"
+      }
+    ]
+  }
+]
  3. 2 tool updates
    • Changedbook1 field changed
      • changedInput schema / examples
        Previous value: -[
-  {
-    "agent": {
-      "name": "Your agent name"
-    },
-    "answers": {
-      "budget": "Not sure yet",
-      "business_name": "Analytical Engines Ltd",
-      "decider": "I decide with a partner",
-      "industry": "Professional services",
-      "notes": "We lose leads that message after hours.",
-      "pains": [
-        "Slow replies to new leads",
-        "Hours of admin and data entry"
-      ],
-      "team_size": "Just me",
-      "timeline": "In the next three months",
-      "website": "analyticalengines.example"
-    },
-    "customer": {
-      "email": "ada@example.com",
-      "name": "Ada Lovelace",
-      "phone": "(619) 555-0123",
-      "time_zone": "Europe/London"
-    },
-    "idempotency_key": "replace-this-with-a-fresh-random-key-0000",
-    "items": [
-      {
-        "slug": "discovery-call"
-      }
-    ],
-    "start": "2026-10-23T08:00:00-07:00"
-  }
-]New value: +[
+  {
+    "agent": {
+      "name": "Your agent name"
+    },
+    "answers": {
+      "budget": "Not sure yet",
+      "business_name": "Analytical Engines Ltd",
+      "decider": "I decide with a partner",
+      "industry": "Professional services",
+      "notes": "We lose leads that message after hours.",
+      "pains": [
+        "Slow replies to new leads",
+        "Hours of admin and data entry"
+      ],
+      "team_size": "Just me",
+      "timeline": "In the next three months",
+      "website": "analyticalengines.example"
+    },
+    "customer": {
+      "email": "ada@example.com",
+      "name": "Ada Lovelace",
+      "phone": "(619) 555-0123",
+      "time_zone": "Europe/London"
+    },
+    "idempotency_key": "replace-this-with-a-fresh-random-key-0000",
+    "items": [
+      {
+        "slug": "discovery-call"
+      }
+    ],
+    "start": "2026-10-24T08:00:00-07:00"
+  }
+]
    • Changedfind_times1 field changed
      • changedInput schema / examples
        Previous value: -[
-  {
-    "from": "2026-10-23",
-    "items": [
-      {
-        "slug": "discovery-call"
-      }
-    ],
-    "to": "2026-10-29",
-    "windows": [
-      {
-        "end": "2026-10-23T13:00:00-07:00",
-        "start": "2026-10-23T08:00:00-07:00"
-      }
-    ]
-  }
-]New value: +[
+  {
+    "from": "2026-10-24",
+    "items": [
+      {
+        "slug": "discovery-call"
+      }
+    ],
+    "to": "2026-10-30",
+    "windows": [
+      {
+        "end": "2026-10-24T13:00:00-07:00",
+        "start": "2026-10-24T08:00:00-07:00"
+      }
+    ]
+  }
+]
  4. 2 tool updates
    • Changedbook1 field changed
      • changedInput schema / examples
        Previous value: -[
-  {
-    "agent": {
-      "name": "Your agent name"
-    },
-    "answers": {
-      "budget": "Not sure yet",
-      "business_name": "Analytical Engines Ltd",
-      "decider": "I decide with a partner",
-      "industry": "Professional services",
-      "notes": "We lose leads that message after hours.",
-      "pains": [
-        "Slow replies to new leads",
-        "Hours of admin and data entry"
-      ],
-      "team_size": "Just me",
-      "timeline": "In the next three months",
-      "website": "analyticalengines.example"
-    },
-    "customer": {
-      "email": "ada@example.com",
-      "name": "Ada Lovelace",
-      "phone": "(619) 555-0123",
-      "time_zone": "Europe/London"
-    },
-    "idempotency_key": "replace-this-with-a-fresh-random-key-0000",
-    "items": [
-      {
-        "slug": "discovery-call"
-      }
-    ],
-    "start": "2026-10-22T08:00:00-07:00"
-  }
-]New value: +[
+  {
+    "agent": {
+      "name": "Your agent name"
+    },
+    "answers": {
+      "budget": "Not sure yet",
+      "business_name": "Analytical Engines Ltd",
+      "decider": "I decide with a partner",
+      "industry": "Professional services",
+      "notes": "We lose leads that message after hours.",
+      "pains": [
+        "Slow replies to new leads",
+        "Hours of admin and data entry"
+      ],
+      "team_size": "Just me",
+      "timeline": "In the next three months",
+      "website": "analyticalengines.example"
+    },
+    "customer": {
+      "email": "ada@example.com",
+      "name": "Ada Lovelace",
+      "phone": "(619) 555-0123",
+      "time_zone": "Europe/London"
+    },
+    "idempotency_key": "replace-this-with-a-fresh-random-key-0000",
+    "items": [
+      {
+        "slug": "discovery-call"
+      }
+    ],
+    "start": "2026-10-23T08:00:00-07:00"
+  }
+]
    • Changedfind_times1 field changed
      • changedInput schema / examples
        Previous value: -[
-  {
-    "from": "2026-10-22",
-    "items": [
-      {
-        "slug": "discovery-call"
-      }
-    ],
-    "to": "2026-10-28",
-    "windows": [
-      {
-        "end": "2026-10-22T18:00:00-07:00",
-        "start": "2026-10-22T08:00:00-07:00"
-      }
-    ]
-  }
-]New value: +[
+  {
+    "from": "2026-10-23",
+    "items": [
+      {
+        "slug": "discovery-call"
+      }
+    ],
+    "to": "2026-10-29",
+    "windows": [
+      {
+        "end": "2026-10-23T13:00:00-07:00",
+        "start": "2026-10-23T08:00:00-07:00"
+      }
+    ]
+  }
+]
  5. 2 tool updates
    • Changedbook1 field changed
      • changedInput schema / examples
        Previous value: -[
-  {
-    "agent": {
-      "name": "Your agent name"
-    },
-    "answers": {
-      "budget": "Not sure yet",
-      "business_name": "Analytical Engines Ltd",
-      "decider": "I decide with a partner",
-      "industry": "Professional services",
-      "notes": "We lose leads that message after hours.",
-      "pains": [
-        "Slow replies to new leads",
-        "Hours of admin and data entry"
-      ],
-      "team_size": "Just me",
-      "timeline": "In the next three months",
-      "website": "analyticalengines.example"
-    },
-    "customer": {
-      "email": "ada@example.com",
-      "name": "Ada Lovelace",
-      "phone": "(619) 555-0123",
-      "time_zone": "Europe/London"
-    },
-    "idempotency_key": "replace-this-with-a-fresh-random-key-0000",
-    "items": [
-      {
-        "slug": "discovery-call"
-      }
-    ],
-    "start": "2026-10-21T08:00:00-07:00"
-  }
-]New value: +[
+  {
+    "agent": {
+      "name": "Your agent name"
+    },
+    "answers": {
+      "budget": "Not sure yet",
+      "business_name": "Analytical Engines Ltd",
+      "decider": "I decide with a partner",
+      "industry": "Professional services",
+      "notes": "We lose leads that message after hours.",
+      "pains": [
+        "Slow replies to new leads",
+        "Hours of admin and data entry"
+      ],
+      "team_size": "Just me",
+      "timeline": "In the next three months",
+      "website": "analyticalengines.example"
+    },
+    "customer": {
+      "email": "ada@example.com",
+      "name": "Ada Lovelace",
+      "phone": "(619) 555-0123",
+      "time_zone": "Europe/London"
+    },
+    "idempotency_key": "replace-this-with-a-fresh-random-key-0000",
+    "items": [
+      {
+        "slug": "discovery-call"
+      }
+    ],
+    "start": "2026-10-22T08:00:00-07:00"
+  }
+]
    • Changedfind_times1 field changed
      • changedInput schema / examples
        Previous value: -[
-  {
-    "from": "2026-10-21",
-    "items": [
-      {
-        "slug": "discovery-call"
-      }
-    ],
-    "to": "2026-10-27",
-    "windows": [
-      {
-        "end": "2026-10-21T18:00:00-07:00",
-        "start": "2026-10-21T08:00:00-07:00"
-      }
-    ]
-  }
-]New value: +[
+  {
+    "from": "2026-10-22",
+    "items": [
+      {
+        "slug": "discovery-call"
+      }
+    ],
+    "to": "2026-10-28",
+    "windows": [
+      {
+        "end": "2026-10-22T18:00:00-07:00",
+        "start": "2026-10-22T08:00:00-07:00"
+      }
+    ]
+  }
+]
  6. 2 tool updates
    • Changedbook1 field changed
      • changedInput schema / examples
        Previous value: -[
-  {
-    "agent": {
-      "name": "Your agent name"
-    },
-    "answers": {
-      "budget": "Not sure yet",
-      "business_name": "Analytical Engines Ltd",
-      "decider": "I decide with a partner",
-      "industry": "Professional services",
-      "notes": "We lose leads that message after hours.",
-      "pains": [
-        "Slow replies to new leads",
-        "Hours of admin and data entry"
-      ],
-      "team_size": "Just me",
-      "timeline": "In the next three months",
-      "website": "analyticalengines.example"
-    },
-    "customer": {
-      "email": "ada@example.com",
-      "name": "Ada Lovelace",
-      "phone": "(619) 555-0123",
-      "time_zone": "Europe/London"
-    },
-    "idempotency_key": "replace-this-with-a-fresh-random-key-0000",
-    "items": [
-      {
-        "slug": "discovery-call"
-      }
-    ],
-    "start": "2026-10-20T08:00:00-07:00"
-  }
-]New value: +[
+  {
+    "agent": {
+      "name": "Your agent name"
+    },
+    "answers": {
+      "budget": "Not sure yet",
+      "business_name": "Analytical Engines Ltd",
+      "decider": "I decide with a partner",
+      "industry": "Professional services",
+      "notes": "We lose leads that message after hours.",
+      "pains": [
+        "Slow replies to new leads",
+        "Hours of admin and data entry"
+      ],
+      "team_size": "Just me",
+      "timeline": "In the next three months",
+      "website": "analyticalengines.example"
+    },
+    "customer": {
+      "email": "ada@example.com",
+      "name": "Ada Lovelace",
+      "phone": "(619) 555-0123",
+      "time_zone": "Europe/London"
+    },
+    "idempotency_key": "replace-this-with-a-fresh-random-key-0000",
+    "items": [
+      {
+        "slug": "discovery-call"
+      }
+    ],
+    "start": "2026-10-21T08:00:00-07:00"
+  }
+]
    • Changedfind_times1 field changed
      • changedInput schema / examples
        Previous value: -[
-  {
-    "from": "2026-10-20",
-    "items": [
-      {
-        "slug": "discovery-call"
-      }
-    ],
-    "to": "2026-10-26",
-    "windows": [
-      {
-        "end": "2026-10-20T13:00:00-07:00",
-        "start": "2026-10-20T08:00:00-07:00"
-      }
-    ]
-  }
-]New value: +[
+  {
+    "from": "2026-10-21",
+    "items": [
+      {
+        "slug": "discovery-call"
+      }
+    ],
+    "to": "2026-10-27",
+    "windows": [
+      {
+        "end": "2026-10-21T18:00:00-07:00",
+        "start": "2026-10-21T08:00:00-07:00"
+      }
+    ]
+  }
+]
  7. 2 tool updates
    • Changedbook1 field changed
      • changedInput schema / examples
        Previous value: -[
-  {
-    "agent": {
-      "name": "Your agent name"
-    },
-    "answers": {
-      "budget": "Not sure yet",
-      "business_name": "Analytical Engines Ltd",
-      "decider": "I decide with a partner",
-      "industry": "Professional services",
-      "notes": "We lose leads that message after hours.",
-      "pains": [
-        "Slow replies to new leads",
-        "Hours of admin and data entry"
-      ],
-      "team_size": "Just me",
-      "timeline": "In the next three months",
-      "website": "analyticalengines.example"
-    },
-    "customer": {
-      "email": "ada@example.com",
-      "name": "Ada Lovelace",
-      "phone": "(619) 555-0123",
-      "time_zone": "Europe/London"
-    },
-    "idempotency_key": "replace-this-with-a-fresh-random-key-0000",
-    "items": [
-      {
-        "slug": "discovery-call"
-      }
-    ],
-    "start": "2026-10-19T08:00:00-07:00"
-  }
-]New value: +[
+  {
+    "agent": {
+      "name": "Your agent name"
+    },
+    "answers": {
+      "budget": "Not sure yet",
+      "business_name": "Analytical Engines Ltd",
+      "decider": "I decide with a partner",
+      "industry": "Professional services",
+      "notes": "We lose leads that message after hours.",
+      "pains": [
+        "Slow replies to new leads",
+        "Hours of admin and data entry"
+      ],
+      "team_size": "Just me",
+      "timeline": "In the next three months",
+      "website": "analyticalengines.example"
+    },
+    "customer": {
+      "email": "ada@example.com",
+      "name": "Ada Lovelace",
+      "phone": "(619) 555-0123",
+      "time_zone": "Europe/London"
+    },
+    "idempotency_key": "replace-this-with-a-fresh-random-key-0000",
+    "items": [
+      {
+        "slug": "discovery-call"
+      }
+    ],
+    "start": "2026-10-20T08:00:00-07:00"
+  }
+]
    • Changedfind_times1 field changed
      • changedInput schema / examples
        Previous value: -[
-  {
-    "from": "2026-10-19",
-    "items": [
-      {
-        "slug": "discovery-call"
-      }
-    ],
-    "to": "2026-10-25",
-    "windows": [
-      {
-        "end": "2026-10-19T18:00:00-07:00",
-        "start": "2026-10-19T08:00:00-07:00"
-      }
-    ]
-  }
-]New value: +[
+  {
+    "from": "2026-10-20",
+    "items": [
+      {
+        "slug": "discovery-call"
+      }
+    ],
+    "to": "2026-10-26",
+    "windows": [
+      {
+        "end": "2026-10-20T13:00:00-07:00",
+        "start": "2026-10-20T08:00:00-07:00"
+      }
+    ]
+  }
+]
  8. 2 tool updates
    • Changedbook1 field changed
      • changedInput schema / examples
        Previous value: -[
-  {
-    "agent": {
-      "name": "Your agent name"
-    },
-    "answers": {
-      "budget": "Not sure yet",
-      "business_name": "Analytical Engines Ltd",
-      "decider": "I decide with a partner",
-      "industry": "Professional services",
-      "notes": "We lose leads that message after hours.",
-      "pains": [
-        "Slow replies to new leads",
-        "Hours of admin and data entry"
-      ],
-      "team_size": "Just me",
-      "timeline": "In the next three months",
-      "website": "analyticalengines.example"
-    },
-    "customer": {
-      "email": "ada@example.com",
-      "name": "Ada Lovelace",
-      "phone": "(619) 555-0123",
-      "time_zone": "Europe/London"
-    },
-    "idempotency_key": "replace-this-with-a-fresh-random-key-0000",
-    "items": [
-      {
-        "slug": "discovery-call"
-      }
-    ],
-    "start": "2026-10-18T08:00:00-07:00"
-  }
-]New value: +[
+  {
+    "agent": {
+      "name": "Your agent name"
+    },
+    "answers": {
+      "budget": "Not sure yet",
+      "business_name": "Analytical Engines Ltd",
+      "decider": "I decide with a partner",
+      "industry": "Professional services",
+      "notes": "We lose leads that message after hours.",
+      "pains": [
+        "Slow replies to new leads",
+        "Hours of admin and data entry"
+      ],
+      "team_size": "Just me",
+      "timeline": "In the next three months",
+      "website": "analyticalengines.example"
+    },
+    "customer": {
+      "email": "ada@example.com",
+      "name": "Ada Lovelace",
+      "phone": "(619) 555-0123",
+      "time_zone": "Europe/London"
+    },
+    "idempotency_key": "replace-this-with-a-fresh-random-key-0000",
+    "items": [
+      {
+        "slug": "discovery-call"
+      }
+    ],
+    "start": "2026-10-19T08:00:00-07:00"
+  }
+]
    • Changedfind_times1 field changed
      • changedInput schema / examples
        Previous value: -[
-  {
-    "from": "2026-10-18",
-    "items": [
-      {
-        "slug": "discovery-call"
-      }
-    ],
-    "to": "2026-10-24",
-    "windows": [
-      {
-        "end": "2026-10-18T13:00:00-07:00",
-        "start": "2026-10-18T08:00:00-07:00"
-      }
-    ]
-  }
-]New value: +[
+  {
+    "from": "2026-10-19",
+    "items": [
+      {
+        "slug": "discovery-call"
+      }
+    ],
+    "to": "2026-10-25",
+    "windows": [
+      {
+        "end": "2026-10-19T18:00:00-07:00",
+        "start": "2026-10-19T08:00:00-07:00"
+      }
+    ]
+  }
+]
  9. 2 tool updates
    • Changedbook1 field changed
      • changedInput schema / examples
        Previous value: -[
-  {
-    "agent": {
-      "name": "Your agent name"
-    },
-    "answers": {
-      "budget": "Not sure yet",
-      "business_name": "Analytical Engines Ltd",
-      "decider": "I decide with a partner",
-      "industry": "Professional services",
-      "notes": "We lose leads that message after hours.",
-      "pains": [
-        "Slow replies to new leads",
-        "Hours of admin and data entry"
-      ],
-      "team_size": "Just me",
-      "timeline": "In the next three months",
-      "website": "analyticalengines.example"
-    },
-    "customer": {
-      "email": "ada@example.com",
-      "name": "Ada Lovelace",
-      "phone": "(619) 555-0123",
-      "time_zone": "Europe/London"
-    },
-    "idempotency_key": "replace-this-with-a-fresh-random-key-0000",
-    "items": [
-      {
-        "slug": "discovery-call"
-      }
-    ],
-    "start": "2026-10-17T08:00:00-07:00"
-  }
-]New value: +[
+  {
+    "agent": {
+      "name": "Your agent name"
+    },
+    "answers": {
+      "budget": "Not sure yet",
+      "business_name": "Analytical Engines Ltd",
+      "decider": "I decide with a partner",
+      "industry": "Professional services",
+      "notes": "We lose leads that message after hours.",
+      "pains": [
+        "Slow replies to new leads",
+        "Hours of admin and data entry"
+      ],
+      "team_size": "Just me",
+      "timeline": "In the next three months",
+      "website": "analyticalengines.example"
+    },
+    "customer": {
+      "email": "ada@example.com",
+      "name": "Ada Lovelace",
+      "phone": "(619) 555-0123",
+      "time_zone": "Europe/London"
+    },
+    "idempotency_key": "replace-this-with-a-fresh-random-key-0000",
+    "items": [
+      {
+        "slug": "discovery-call"
+      }
+    ],
+    "start": "2026-10-18T08:00:00-07:00"
+  }
+]
    • Changedfind_times1 field changed
      • changedInput schema / examples
        Previous value: -[
-  {
-    "from": "2026-10-17",
-    "items": [
-      {
-        "slug": "discovery-call"
-      }
-    ],
-    "to": "2026-10-23",
-    "windows": [
-      {
-        "end": "2026-10-17T13:00:00-07:00",
-        "start": "2026-10-17T08:00:00-07:00"
-      }
-    ]
-  }
-]New value: +[
+  {
+    "from": "2026-10-18",
+    "items": [
+      {
+        "slug": "discovery-call"
+      }
+    ],
+    "to": "2026-10-24",
+    "windows": [
+      {
+        "end": "2026-10-18T13:00:00-07:00",
+        "start": "2026-10-18T08:00:00-07:00"
+      }
+    ]
+  }
+]
  10. 2 tool updates
    • Changedbook1 field changed
      • changedInput schema / examples
        Previous value: -[
-  {
-    "agent": {
-      "name": "Your agent name"
-    },
-    "answers": {
-      "budget": "Not sure yet",
-      "business_name": "Analytical Engines Ltd",
-      "decider": "I decide with a partner",
-      "industry": "Professional services",
-      "notes": "We lose leads that message after hours.",
-      "pains": [
-        "Slow replies to new leads",
-        "Hours of admin and data entry"
-      ],
-      "team_size": "Just me",
-      "timeline": "In the next three months",
-      "website": "analyticalengines.example"
-    },
-    "customer": {
-      "email": "ada@example.com",
-      "name": "Ada Lovelace",
-      "phone": "(619) 555-0123",
-      "time_zone": "Europe/London"
-    },
-    "idempotency_key": "replace-this-with-a-fresh-random-key-0000",
-    "items": [
-      {
-        "slug": "discovery-call"
-      }
-    ],
-    "start": "2026-10-16T08:00:00-07:00"
-  }
-]New value: +[
+  {
+    "agent": {
+      "name": "Your agent name"
+    },
+    "answers": {
+      "budget": "Not sure yet",
+      "business_name": "Analytical Engines Ltd",
+      "decider": "I decide with a partner",
+      "industry": "Professional services",
+      "notes": "We lose leads that message after hours.",
+      "pains": [
+        "Slow replies to new leads",
+        "Hours of admin and data entry"
+      ],
+      "team_size": "Just me",
+      "timeline": "In the next three months",
+      "website": "analyticalengines.example"
+    },
+    "customer": {
+      "email": "ada@example.com",
+      "name": "Ada Lovelace",
+      "phone": "(619) 555-0123",
+      "time_zone": "Europe/London"
+    },
+    "idempotency_key": "replace-this-with-a-fresh-random-key-0000",
+    "items": [
+      {
+        "slug": "discovery-call"
+      }
+    ],
+    "start": "2026-10-17T08:00:00-07:00"
+  }
+]
    • Changedfind_times1 field changed
      • changedInput schema / examples
        Previous value: -[
-  {
-    "from": "2026-10-16",
-    "items": [
-      {
-        "slug": "discovery-call"
-      }
-    ],
-    "to": "2026-10-22",
-    "windows": [
-      {
-        "end": "2026-10-16T13:00:00-07:00",
-        "start": "2026-10-16T08:00:00-07:00"
-      }
-    ]
-  }
-]New value: +[
+  {
+    "from": "2026-10-17",
+    "items": [
+      {
+        "slug": "discovery-call"
+      }
+    ],
+    "to": "2026-10-23",
+    "windows": [
+      {
+        "end": "2026-10-17T13:00:00-07:00",
+        "start": "2026-10-17T08:00:00-07:00"
+      }
+    ]
+  }
+]
  11. 2 tool updates
    • Changedbook1 field changed
      • changedInput schema / examples
        Previous value: -[
-  {
-    "agent": {
-      "name": "Your agent name"
-    },
-    "answers": {
-      "budget": "Not sure yet",
-      "business_name": "Analytical Engines Ltd",
-      "decider": "I decide with a partner",
-      "industry": "Professional services",
-      "notes": "We lose leads that message after hours.",
-      "pains": [
-        "Slow replies to new leads",
-        "Hours of admin and data entry"
-      ],
-      "team_size": "Just me",
-      "timeline": "In the next three months",
-      "website": "analyticalengines.example"
-    },
-    "customer": {
-      "email": "ada@example.com",
-      "name": "Ada Lovelace",
-      "phone": "(619) 555-0123",
-      "time_zone": "Europe/London"
-    },
-    "idempotency_key": "replace-this-with-a-fresh-random-key-0000",
-    "items": [
-      {
-        "slug": "discovery-call"
-      }
-    ],
-    "start": "2026-10-14T08:00:00-07:00"
-  }
-]New value: +[
+  {
+    "agent": {
+      "name": "Your agent name"
+    },
+    "answers": {
+      "budget": "Not sure yet",
+      "business_name": "Analytical Engines Ltd",
+      "decider": "I decide with a partner",
+      "industry": "Professional services",
+      "notes": "We lose leads that message after hours.",
+      "pains": [
+        "Slow replies to new leads",
+        "Hours of admin and data entry"
+      ],
+      "team_size": "Just me",
+      "timeline": "In the next three months",
+      "website": "analyticalengines.example"
+    },
+    "customer": {
+      "email": "ada@example.com",
+      "name": "Ada Lovelace",
+      "phone": "(619) 555-0123",
+      "time_zone": "Europe/London"
+    },
+    "idempotency_key": "replace-this-with-a-fresh-random-key-0000",
+    "items": [
+      {
+        "slug": "discovery-call"
+      }
+    ],
+    "start": "2026-10-16T08:00:00-07:00"
+  }
+]
    • Changedfind_times1 field changed
      • changedInput schema / examples
        Previous value: -[
-  {
-    "from": "2026-10-14",
-    "items": [
-      {
-        "slug": "discovery-call"
-      }
-    ],
-    "to": "2026-10-20",
-    "windows": [
-      {
-        "end": "2026-10-14T18:00:00-07:00",
-        "start": "2026-10-14T08:00:00-07:00"
-      }
-    ]
-  }
-]New value: +[
+  {
+    "from": "2026-10-16",
+    "items": [
+      {
+        "slug": "discovery-call"
+      }
+    ],
+    "to": "2026-10-22",
+    "windows": [
+      {
+        "end": "2026-10-16T13:00:00-07:00",
+        "start": "2026-10-16T08:00:00-07:00"
+      }
+    ]
+  }
+]
  12. 2 tool updates
    • Changedbook1 field changed
      • changedInput schema / examples
        Previous value: -[
-  {
-    "agent": {
-      "name": "Your agent name"
-    },
-    "answers": {
-      "budget": "Not sure yet",
-      "business_name": "Analytical Engines Ltd",
-      "decider": "I decide with a partner",
-      "industry": "Professional services",
-      "notes": "We lose leads that message after hours.",
-      "pains": [
-        "Slow replies to new leads",
-        "Hours of admin and data entry"
-      ],
-      "team_size": "Just me",
-      "timeline": "In the next three months",
-      "website": "analyticalengines.example"
-    },
-    "customer": {
-      "email": "ada@example.com",
-      "name": "Ada Lovelace",
-      "phone": "(619) 555-0123",
-      "time_zone": "Europe/London"
-    },
-    "idempotency_key": "replace-this-with-a-fresh-random-key-0000",
-    "items": [
-      {
-        "slug": "discovery-call"
-      }
-    ],
-    "start": "2026-10-13T08:00:00-07:00"
-  }
-]New value: +[
+  {
+    "agent": {
+      "name": "Your agent name"
+    },
+    "answers": {
+      "budget": "Not sure yet",
+      "business_name": "Analytical Engines Ltd",
+      "decider": "I decide with a partner",
+      "industry": "Professional services",
+      "notes": "We lose leads that message after hours.",
+      "pains": [
+        "Slow replies to new leads",
+        "Hours of admin and data entry"
+      ],
+      "team_size": "Just me",
+      "timeline": "In the next three months",
+      "website": "analyticalengines.example"
+    },
+    "customer": {
+      "email": "ada@example.com",
+      "name": "Ada Lovelace",
+      "phone": "(619) 555-0123",
+      "time_zone": "Europe/London"
+    },
+    "idempotency_key": "replace-this-with-a-fresh-random-key-0000",
+    "items": [
+      {
+        "slug": "discovery-call"
+      }
+    ],
+    "start": "2026-10-14T08:00:00-07:00"
+  }
+]
    • Changedfind_times1 field changed
      • changedInput schema / examples
        Previous value: -[
-  {
-    "from": "2026-10-13",
-    "items": [
-      {
-        "slug": "discovery-call"
-      }
-    ],
-    "to": "2026-10-19",
-    "windows": [
-      {
-        "end": "2026-10-13T13:00:00-07:00",
-        "start": "2026-10-13T08:00:00-07:00"
-      }
-    ]
-  }
-]New value: +[
+  {
+    "from": "2026-10-14",
+    "items": [
+      {
+        "slug": "discovery-call"
+      }
+    ],
+    "to": "2026-10-20",
+    "windows": [
+      {
+        "end": "2026-10-14T18:00:00-07:00",
+        "start": "2026-10-14T08:00:00-07:00"
+      }
+    ]
+  }
+]
  13. 2 tool updates
    • Changedbook1 field changed
      • changedInput schema / examples
        Previous value: -[
-  {
-    "agent": {
-      "name": "Your agent name"
-    },
-    "answers": {
-      "budget": "Not sure yet",
-      "business_name": "Analytical Engines Ltd",
-      "decider": "I decide with a partner",
-      "industry": "Professional services",
-      "notes": "We lose leads that message after hours.",
-      "pains": [
-        "Slow replies to new leads",
-        "Hours of admin and data entry"
-      ],
-      "team_size": "Just me",
-      "timeline": "In the next three months",
-      "website": "analyticalengines.example"
-    },
-    "customer": {
-      "email": "ada@example.com",
-      "name": "Ada Lovelace",
-      "phone": "(619) 555-0123",
-      "time_zone": "Europe/London"
-    },
-    "idempotency_key": "replace-this-with-a-fresh-random-key-0000",
-    "items": [
-      {
-        "slug": "discovery-call"
-      }
-    ],
-    "start": "2026-10-12T08:00:00-07:00"
-  }
-]New value: +[
+  {
+    "agent": {
+      "name": "Your agent name"
+    },
+    "answers": {
+      "budget": "Not sure yet",
+      "business_name": "Analytical Engines Ltd",
+      "decider": "I decide with a partner",
+      "industry": "Professional services",
+      "notes": "We lose leads that message after hours.",
+      "pains": [
+        "Slow replies to new leads",
+        "Hours of admin and data entry"
+      ],
+      "team_size": "Just me",
+      "timeline": "In the next three months",
+      "website": "analyticalengines.example"
+    },
+    "customer": {
+      "email": "ada@example.com",
+      "name": "Ada Lovelace",
+      "phone": "(619) 555-0123",
+      "time_zone": "Europe/London"
+    },
+    "idempotency_key": "replace-this-with-a-fresh-random-key-0000",
+    "items": [
+      {
+        "slug": "discovery-call"
+      }
+    ],
+    "start": "2026-10-13T08:00:00-07:00"
+  }
+]
    • Changedfind_times1 field changed
      • changedInput schema / examples
        Previous value: -[
-  {
-    "from": "2026-10-12",
-    "items": [
-      {
-        "slug": "discovery-call"
-      }
-    ],
-    "to": "2026-10-18",
-    "windows": [
-      {
-        "end": "2026-10-12T18:00:00-07:00",
-        "start": "2026-10-12T08:00:00-07:00"
-      }
-    ]
-  }
-]New value: +[
+  {
+    "from": "2026-10-13",
+    "items": [
+      {
+        "slug": "discovery-call"
+      }
+    ],
+    "to": "2026-10-19",
+    "windows": [
+      {
+        "end": "2026-10-13T13:00:00-07:00",
+        "start": "2026-10-13T08:00:00-07:00"
+      }
+    ]
+  }
+]
  14. 2 tool updates
    • Changedbook1 field changed
      • changedInput schema / examples
        Previous value: -[
-  {
-    "agent": {
-      "name": "Your agent name"
-    },
-    "answers": {
-      "budget": "Not sure yet",
-      "business_name": "Analytical Engines Ltd",
-      "decider": "I decide with a partner",
-      "industry": "Professional services",
-      "notes": "We lose leads that message after hours.",
-      "pains": [
-        "Slow replies to new leads",
-        "Hours of admin and data entry"
-      ],
-      "team_size": "Just me",
-      "timeline": "In the next three months",
-      "website": "analyticalengines.example"
-    },
-    "customer": {
-      "email": "ada@example.com",
-      "name": "Ada Lovelace",
-      "phone": "(619) 555-0123",
-      "time_zone": "Europe/London"
-    },
-    "idempotency_key": "replace-this-with-a-fresh-random-key-0000",
-    "items": [
-      {
-        "slug": "discovery-call"
-      }
-    ],
-    "start": "2026-10-11T08:00:00-07:00"
-  }
-]New value: +[
+  {
+    "agent": {
+      "name": "Your agent name"
+    },
+    "answers": {
+      "budget": "Not sure yet",
+      "business_name": "Analytical Engines Ltd",
+      "decider": "I decide with a partner",
+      "industry": "Professional services",
+      "notes": "We lose leads that message after hours.",
+      "pains": [
+        "Slow replies to new leads",
+        "Hours of admin and data entry"
+      ],
+      "team_size": "Just me",
+      "timeline": "In the next three months",
+      "website": "analyticalengines.example"
+    },
+    "customer": {
+      "email": "ada@example.com",
+      "name": "Ada Lovelace",
+      "phone": "(619) 555-0123",
+      "time_zone": "Europe/London"
+    },
+    "idempotency_key": "replace-this-with-a-fresh-random-key-0000",
+    "items": [
+      {
+        "slug": "discovery-call"
+      }
+    ],
+    "start": "2026-10-12T08:00:00-07:00"
+  }
+]
    • Changedfind_times1 field changed
      • changedInput schema / examples
        Previous value: -[
-  {
-    "from": "2026-10-11",
-    "items": [
-      {
-        "slug": "discovery-call"
-      }
-    ],
-    "to": "2026-10-17",
-    "windows": [
-      {
-        "end": "2026-10-11T13:00:00-07:00",
-        "start": "2026-10-11T08:00:00-07:00"
-      }
-    ]
-  }
-]New value: +[
+  {
+    "from": "2026-10-12",
+    "items": [
+      {
+        "slug": "discovery-call"
+      }
+    ],
+    "to": "2026-10-18",
+    "windows": [
+      {
+        "end": "2026-10-12T18:00:00-07:00",
+        "start": "2026-10-12T08:00:00-07:00"
+      }
+    ]
+  }
+]
  15. 2 tool updates
    • Changedbook1 field changed
      • changedInput schema / examples
        Previous value: -[
-  {
-    "agent": {
-      "name": "Your agent name"
-    },
-    "answers": {
-      "budget": "Not sure yet",
-      "business_name": "Analytical Engines Ltd",
-      "decider": "I decide with a partner",
-      "industry": "Professional services",
-      "notes": "We lose leads that message after hours.",
-      "pains": [
-        "Slow replies to new leads",
-        "Hours of admin and data entry"
-      ],
-      "team_size": "Just me",
-      "timeline": "In the next three months",
-      "website": "analyticalengines.example"
-    },
-    "customer": {
-      "email": "ada@example.com",
-      "name": "Ada Lovelace",
-      "phone": "(619) 555-0123",
-      "time_zone": "Europe/London"
-    },
-    "idempotency_key": "replace-this-with-a-fresh-random-key-0000",
-    "items": [
-      {
-        "slug": "discovery-call"
-      }
-    ],
-    "start": "2026-10-10T08:00:00-07:00"
-  }
-]New value: +[
+  {
+    "agent": {
+      "name": "Your agent name"
+    },
+    "answers": {
+      "budget": "Not sure yet",
+      "business_name": "Analytical Engines Ltd",
+      "decider": "I decide with a partner",
+      "industry": "Professional services",
+      "notes": "We lose leads that message after hours.",
+      "pains": [
+        "Slow replies to new leads",
+        "Hours of admin and data entry"
+      ],
+      "team_size": "Just me",
+      "timeline": "In the next three months",
+      "website": "analyticalengines.example"
+    },
+    "customer": {
+      "email": "ada@example.com",
+      "name": "Ada Lovelace",
+      "phone": "(619) 555-0123",
+      "time_zone": "Europe/London"
+    },
+    "idempotency_key": "replace-this-with-a-fresh-random-key-0000",
+    "items": [
+      {
+        "slug": "discovery-call"
+      }
+    ],
+    "start": "2026-10-11T08:00:00-07:00"
+  }
+]
    • Changedfind_times1 field changed
      • changedInput schema / examples
        Previous value: -[
-  {
-    "from": "2026-10-10",
-    "items": [
-      {
-        "slug": "discovery-call"
-      }
-    ],
-    "to": "2026-10-16",
-    "windows": [
-      {
-        "end": "2026-10-10T13:00:00-07:00",
-        "start": "2026-10-10T08:00:00-07:00"
-      }
-    ]
-  }
-]New value: +[
+  {
+    "from": "2026-10-11",
+    "items": [
+      {
+        "slug": "discovery-call"
+      }
+    ],
+    "to": "2026-10-17",
+    "windows": [
+      {
+        "end": "2026-10-11T13:00:00-07:00",
+        "start": "2026-10-11T08:00:00-07:00"
+      }
+    ]
+  }
+]
  16. 2 tool updates
    • Changedbook1 field changed
      • changedInput schema / examples
        Previous value: -[
-  {
-    "agent": {
-      "name": "Your agent name"
-    },
-    "answers": {
-      "budget": "Not sure yet",
-      "business_name": "Analytical Engines Ltd",
-      "decider": "I decide with a partner",
-      "industry": "Professional services",
-      "notes": "We lose leads that message after hours.",
-      "pains": [
-        "Slow replies to new leads",
-        "Hours of admin and data entry"
-      ],
-      "team_size": "Just me",
-      "timeline": "In the next three months",
-      "website": "analyticalengines.example"
-    },
-    "customer": {
-      "email": "ada@example.com",
-      "name": "Ada Lovelace",
-      "phone": "(619) 555-0123",
-      "time_zone": "Europe/London"
-    },
-    "idempotency_key": "replace-this-with-a-fresh-random-key-0000",
-    "items": [
-      {
-        "slug": "discovery-call"
-      }
-    ],
-    "start": "2026-10-09T08:00:00-07:00"
-  }
-]New value: +[
+  {
+    "agent": {
+      "name": "Your agent name"
+    },
+    "answers": {
+      "budget": "Not sure yet",
+      "business_name": "Analytical Engines Ltd",
+      "decider": "I decide with a partner",
+      "industry": "Professional services",
+      "notes": "We lose leads that message after hours.",
+      "pains": [
+        "Slow replies to new leads",
+        "Hours of admin and data entry"
+      ],
+      "team_size": "Just me",
+      "timeline": "In the next three months",
+      "website": "analyticalengines.example"
+    },
+    "customer": {
+      "email": "ada@example.com",
+      "name": "Ada Lovelace",
+      "phone": "(619) 555-0123",
+      "time_zone": "Europe/London"
+    },
+    "idempotency_key": "replace-this-with-a-fresh-random-key-0000",
+    "items": [
+      {
+        "slug": "discovery-call"
+      }
+    ],
+    "start": "2026-10-10T08:00:00-07:00"
+  }
+]
    • Changedfind_times1 field changed
      • changedInput schema / examples
        Previous value: -[
-  {
-    "from": "2026-10-09",
-    "items": [
-      {
-        "slug": "discovery-call"
-      }
-    ],
-    "to": "2026-10-15",
-    "windows": [
-      {
-        "end": "2026-10-09T13:00:00-07:00",
-        "start": "2026-10-09T08:00:00-07:00"
-      }
-    ]
-  }
-]New value: +[
+  {
+    "from": "2026-10-10",
+    "items": [
+      {
+        "slug": "discovery-call"
+      }
+    ],
+    "to": "2026-10-16",
+    "windows": [
+      {
+        "end": "2026-10-10T13:00:00-07:00",
+        "start": "2026-10-10T08:00:00-07:00"
+      }
+    ]
+  }
+]
  17. 2 tool updates
    • Changedbook1 field changed
      • changedInput schema / examples
        Previous value: -[
-  {
-    "agent": {
-      "name": "Your agent name"
-    },
-    "answers": {
-      "budget": "Not sure yet",
-      "business_name": "Analytical Engines Ltd",
-      "decider": "I decide with a partner",
-      "industry": "Professional services",
-      "notes": "We lose leads that message after hours.",
-      "pains": [
-        "Slow replies to new leads",
-        "Hours of admin and data entry"
-      ],
-      "team_size": "Just me",
-      "timeline": "In the next three months",
-      "website": "analyticalengines.example"
-    },
-    "customer": {
-      "email": "ada@example.com",
-      "name": "Ada Lovelace",
-      "phone": "(619) 555-0123",
-      "time_zone": "Europe/London"
-    },
-    "idempotency_key": "replace-this-with-a-fresh-random-key-0000",
-    "items": [
-      {
-        "slug": "discovery-call"
-      }
-    ],
-    "start": "2026-10-08T08:00:00-07:00"
-  }
-]New value: +[
+  {
+    "agent": {
+      "name": "Your agent name"
+    },
+    "answers": {
+      "budget": "Not sure yet",
+      "business_name": "Analytical Engines Ltd",
+      "decider": "I decide with a partner",
+      "industry": "Professional services",
+      "notes": "We lose leads that message after hours.",
+      "pains": [
+        "Slow replies to new leads",
+        "Hours of admin and data entry"
+      ],
+      "team_size": "Just me",
+      "timeline": "In the next three months",
+      "website": "analyticalengines.example"
+    },
+    "customer": {
+      "email": "ada@example.com",
+      "name": "Ada Lovelace",
+      "phone": "(619) 555-0123",
+      "time_zone": "Europe/London"
+    },
+    "idempotency_key": "replace-this-with-a-fresh-random-key-0000",
+    "items": [
+      {
+        "slug": "discovery-call"
+      }
+    ],
+    "start": "2026-10-09T08:00:00-07:00"
+  }
+]
    • Changedfind_times1 field changed
      • changedInput schema / examples
        Previous value: -[
-  {
-    "from": "2026-10-08",
-    "items": [
-      {
-        "slug": "discovery-call"
-      }
-    ],
-    "to": "2026-10-14",
-    "windows": [
-      {
-        "end": "2026-10-08T18:00:00-07:00",
-        "start": "2026-10-08T08:00:00-07:00"
-      }
-    ]
-  }
-]New value: +[
+  {
+    "from": "2026-10-09",
+    "items": [
+      {
+        "slug": "discovery-call"
+      }
+    ],
+    "to": "2026-10-15",
+    "windows": [
+      {
+        "end": "2026-10-09T13:00:00-07:00",
+        "start": "2026-10-09T08:00:00-07:00"
+      }
+    ]
+  }
+]
  18. 2 tool updates
    • Changedbook1 field changed
      • changedInput schema / examples
        Previous value: -[
-  {
-    "agent": {
-      "name": "Your agent name"
-    },
-    "answers": {
-      "budget": "Not sure yet",
-      "business_name": "Analytical Engines Ltd",
-      "decider": "I decide with a partner",
-      "industry": "Professional services",
-      "notes": "We lose leads that message after hours.",
-      "pains": [
-        "Slow replies to new leads",
-        "Hours of admin and data entry"
-      ],
-      "team_size": "Just me",
-      "timeline": "In the next three months",
-      "website": "analyticalengines.example"
-    },
-    "customer": {
-      "email": "ada@example.com",
-      "name": "Ada Lovelace",
-      "phone": "(619) 555-0123",
-      "time_zone": "Europe/London"
-    },
-    "idempotency_key": "replace-this-with-a-fresh-random-key-0000",
-    "items": [
-      {
-        "slug": "discovery-call"
-      }
-    ],
-    "start": "2026-10-07T08:00:00-07:00"
-  }
-]New value: +[
+  {
+    "agent": {
+      "name": "Your agent name"
+    },
+    "answers": {
+      "budget": "Not sure yet",
+      "business_name": "Analytical Engines Ltd",
+      "decider": "I decide with a partner",
+      "industry": "Professional services",
+      "notes": "We lose leads that message after hours.",
+      "pains": [
+        "Slow replies to new leads",
+        "Hours of admin and data entry"
+      ],
+      "team_size": "Just me",
+      "timeline": "In the next three months",
+      "website": "analyticalengines.example"
+    },
+    "customer": {
+      "email": "ada@example.com",
+      "name": "Ada Lovelace",
+      "phone": "(619) 555-0123",
+      "time_zone": "Europe/London"
+    },
+    "idempotency_key": "replace-this-with-a-fresh-random-key-0000",
+    "items": [
+      {
+        "slug": "discovery-call"
+      }
+    ],
+    "start": "2026-10-08T08:00:00-07:00"
+  }
+]
    • Changedfind_times1 field changed
      • changedInput schema / examples
        Previous value: -[
-  {
-    "from": "2026-10-07",
-    "items": [
-      {
-        "slug": "discovery-call"
-      }
-    ],
-    "to": "2026-10-13",
-    "windows": [
-      {
-        "end": "2026-10-07T18:00:00-07:00",
-        "start": "2026-10-07T08:00:00-07:00"
-      }
-    ]
-  }
-]New value: +[
+  {
+    "from": "2026-10-08",
+    "items": [
+      {
+        "slug": "discovery-call"
+      }
+    ],
+    "to": "2026-10-14",
+    "windows": [
+      {
+        "end": "2026-10-08T18:00:00-07:00",
+        "start": "2026-10-08T08:00:00-07:00"
+      }
+    ]
+  }
+]
  19. 2 tool updates
    • Changedbook1 field changed
      • changedInput schema / examples
        Previous value: -[
-  {
-    "agent": {
-      "name": "Your agent name"
-    },
-    "answers": {
-      "budget": "Not sure yet",
-      "business_name": "Analytical Engines Ltd",
-      "decider": "I decide with a partner",
-      "industry": "Professional services",
-      "notes": "We lose leads that message after hours.",
-      "pains": [
-        "Slow replies to new leads",
-        "Hours of admin and data entry"
-      ],
-      "team_size": "Just me",
-      "timeline": "In the next three months",
-      "website": "analyticalengines.example"
-    },
-    "customer": {
-      "email": "ada@example.com",
-      "name": "Ada Lovelace",
-      "phone": "(619) 555-0123",
-      "time_zone": "Europe/London"
-    },
-    "idempotency_key": "replace-this-with-a-fresh-random-key-0000",
-    "items": [
-      {
-        "slug": "discovery-call"
-      }
-    ],
-    "start": "2026-10-06T08:00:00-07:00"
-  }
-]New value: +[
+  {
+    "agent": {
+      "name": "Your agent name"
+    },
+    "answers": {
+      "budget": "Not sure yet",
+      "business_name": "Analytical Engines Ltd",
+      "decider": "I decide with a partner",
+      "industry": "Professional services",
+      "notes": "We lose leads that message after hours.",
+      "pains": [
+        "Slow replies to new leads",
+        "Hours of admin and data entry"
+      ],
+      "team_size": "Just me",
+      "timeline": "In the next three months",
+      "website": "analyticalengines.example"
+    },
+    "customer": {
+      "email": "ada@example.com",
+      "name": "Ada Lovelace",
+      "phone": "(619) 555-0123",
+      "time_zone": "Europe/London"
+    },
+    "idempotency_key": "replace-this-with-a-fresh-random-key-0000",
+    "items": [
+      {
+        "slug": "discovery-call"
+      }
+    ],
+    "start": "2026-10-07T08:00:00-07:00"
+  }
+]
    • Changedfind_times1 field changed
      • changedInput schema / examples
        Previous value: -[
-  {
-    "from": "2026-10-06",
-    "items": [
-      {
-        "slug": "discovery-call"
-      }
-    ],
-    "to": "2026-10-12",
-    "windows": [
-      {
-        "end": "2026-10-06T13:00:00-07:00",
-        "start": "2026-10-06T08:00:00-07:00"
-      }
-    ]
-  }
-]New value: +[
+  {
+    "from": "2026-10-07",
+    "items": [
+      {
+        "slug": "discovery-call"
+      }
+    ],
+    "to": "2026-10-13",
+    "windows": [
+      {
+        "end": "2026-10-07T18:00:00-07:00",
+        "start": "2026-10-07T08:00:00-07:00"
+      }
+    ]
+  }
+]

Related MCP Connectors

Related MCP Servers

  • G-Guest MCP server

    BlondeDevRules
    A
    license
    A
    quality
    A
    maintenance
    Book a table, an appointment or a place in a class at a real local business. Live availability, instant confirmation, no account and no API key. Eight tools: search, fetch, get_business, check_availability, create_booking, check_booking, cancel_booking and request_listing. Guest emails in eight languages. Hosted at https://g-guest.app/api/mcp
    8
    6 npm
    MIT

  • CallChatSyn MCP Server

    oneappsworld
    A
    license
    A
    quality
    A
    maintenance
    Enables AI assistants to answer a small business's customer questions from its own FAQs and order data, list upcoming open appointment times in the business's time zone, and book one of those offered slots with staff notification. Free for the first 1,000 businesses, using fast rule-based FAQ matching rather than free-form generation.
    3
    MIT

  • Ambient

    mukeshkbj
    A
    license
    Not graded
    quality
    B
    maintenance
    Enables an Alexa+ agent to place business calls on the owner’s behalf, disclose that it is an AI, enforce spending limits with owner approval, and book only when a clean yes confirms the read-back terms.
    5 npm
    MIT
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources