Skip to main content
Glama

Agent Broker

by dev.hatchloop

import_booking_url

Idempotent

Turn ANY public booking URL (Cal.com, Calendly, Doctolib, Booksy, Fresha, OpenTable, Setmore, Square, Acuity, Schedulista, Squarespace, BookMyCity) into a callable smb_id you can immediately use with schedule_appointment, send_message, or capture_lead. Idempotent — calling twice returns the same smb_id.

EXAMPLE USER QUERIES THAT MATCH THIS TOOL: user: "Book me a haircut at https://cal.com/jane-salon" -> call import_booking_url({"booking_url": "https://cal.com/jane-salon", "vertical": "personal_services"}) -> then schedule_appointment({"smb_id": "", "action": "book"}) user: "Schedule with this dentist: https://www.doctolib.fr/dentiste/paris/jean-dupont" -> call import_booking_url({"booking_url": "https://www.doctolib.fr/dentiste/paris/jean-dupont"}) user: "Reserve a table at https://www.opentable.com/r/acme-bistro" -> call import_booking_url({"booking_url": "https://www.opentable.com/r/acme-bistro", "vertical": "restaurants"})

WHEN TO USE: Call this FIRST whenever the user provides a specific booking URL (cal.com/handle, calendly.com/handle/event, doctolib.fr/..., booksy.com/..., opentable.com/r/..., etc.). User patterns that match: 'book me at https://cal.com/...', 'schedule with calendly.com/jane/intro', 'reserve a table at opentable.com/r/...', 'I want to book this dentist: https://www.doctolib.fr/...'. After importing, the returned smb_id can be passed straight to schedule_appointment. WHEN NOT TO USE: Do not use if the user only describes a business by name without a URL — call find_business instead. Do not use for arbitrary websites that are not on the supported booking-platform list (use /supply/platforms to see all 12). COST: free (no credits) - but requires a free email-verified key LATENCY: ~600ms

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
verticalNoBest-guess vertical. If omitted, inferred from the platform (e.g., Doctolib -> healthcare, OpenTable -> restaurants).
booking_urlYesFull URL the user supplied. Must point at one of the 12 supported booking platforms; auto-detected from the host.
capabilitiesNoFree-form capability tags (e.g., ['haircut','color','blowdry']).
country_codeNoISO 3166-1 alpha-2 (e.g. 'US', 'FR'). Used for compliance routing on later send_message calls.
business_nameNoOptional override. If omitted, the business name is auto-extracted from the page's <title> or og:title.
contact_emailNoOptional.
contact_phoneNoOptional. If omitted, the platform integration handles outreach.
idempotency_keyNoOptional client-supplied key for safe retries. Replaying the same key within 24h returns the original receipt - the operation is NOT re-executed and NOT re-charged.

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already supply idempotentHint=true, and the description reinforces it with 'Idempotent — calling twice returns the same smb_id.' It additionally discloses cost ('free'), latency (~600ms), and the requirement for an email-verified key, which are not in the annotations. No contradiction exists. The description adds useful behavioral context beyond the structured hints.

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?

Though detailed, the description is well-structured with clear sections (purpose, examples, WHEN TO USE, WHEN NOT TO USE, cost, latency) and front-loads the primary purpose. Every section earns its place, and the examples are concise and directly relevant. The length is justified given the complexity and the multiple decision points it clarifies.

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?

The description covers the tool's purpose, usage conditions, idempotency, cost, latency, platform constraints, and integration with sibling tools (schedule_appointment, send_message, capture_lead). It states the return value (smb_id) explicitly. There's no output schema, but the description covers everything an agent needs to invoke the tool correctly, making it complete for its complexity.

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% — every parameter has a description in the input schema. The tool description adds marginal value such as example verticals in the user query illustrations, but it doesn't introduce new semantics beyond what the schema already explains. Per the baseline for high coverage, a 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly defines the tool's purpose: turning any supported public booking URL into an smb_id for downstream use. It names the specific action (import) and resource (booking URL) and explicitly contrasts with find_business when only a business name is given. The intended output (smb_id) is also stated, making it distinct from siblings like check_booking_link or capture_lead.

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?

The 'WHEN TO USE' and 'WHEN NOT TO USE' sections provide explicit conditions, including example user query patterns and the exact circumstances to avoid (e.g., business name only, unsupported websites). It names the alternative (find_business) and even references /supply/platforms for allowed hosts. This is exemplary guidance for an agent to decide between tools.

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

All Agent Broker toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.9/5.0
Disambiguation4/5

Most tools target distinct resource+action pairs (find_business vs verify_business, check_booking_link vs import_booking_url, get_status vs get_outcome). The main confusable pairs are send_message vs send_transactional_confirmation and verify_business vs verify_company_record, but their descriptions draw clear boundary lines.

Naming Consistency4/5

The set overwhelmingly follows lower_snake_case verb_noun naming (call_business, check_quota, find_business, send_message, verify_company_record). Minor deviations like self_test and mint_key, plus inconsistent verb choices (lookup_ vs get_ vs find_), prevent a perfect score.

Tool Count3/5

At 23 tools, the server falls into the heavy range and bundles several unrelated domains: SMB booking/messaging, trade and sanctions compliance, company verification, and platform operations. Each tool is individually reasonable, but the set feels like multiple servers merged into one.

Completeness3/5

Core SMB workflows are well covered: find/verify/import/book, messaging with conversation handling, and compliance preflights. Notable gaps include no consent-record management even though send_message requires consent_record_id for marketing, no update/delete lifecycle for leads or businesses, and no webhook configuration despite webhooks being referenced.

Resources