Skip to main content
Glama

Agent Broker

by io.github.basilalshukaili

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.6/5.0
Behavior5/5

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

Beyond the idempotentHint annotation, the description discloses cost implications (free but requires email-verified key), approximate latency, auto-detection of platform from host, and automatic extraction of vertical/business name when omitted. These are behavioral details not present in annotations or schema.

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 long but each section earns its place: opening summary, realistic examples, explicit usage criteria, cost, and latency. It is front-loaded with the core transformation and output, with supporting details structured under clear headings.

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 tool with no output schema, the description conveys the key output (smb_id), the idempotent receipt behavior, and downstream usage, which covers the critical integration handoff. It stops short of specifying the exact response field structure, but the examples and 'returns the same smb_id' language are sufficient for an agent to proceed.

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%, so the schema already documents all parameters thoroughly, including vertical inference, country_code compliance use, business_name extraction fallback, and idempotency_key replay semantics. The description reinforces this with usage examples but does not add new parameter meaning beyond the schema.

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 names the exact operation ('Turn ANY public booking URL ... into a callable smb_id'), enumerates supported platforms, and frames the tool as the import step before schedule_appointment, send_message, or capture_lead. It also explicitly contrasts with find_business in the WHEN NOT TO USE section, removing ambiguity among siblings.

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 description contains dedicated WHEN TO USE and WHEN NOT TO USE sections, gives concrete user-query patterns that match, and names the alternative (find_business) for the non-URL case. This is explicit routing guidance, not just implied context.

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

A4.5/5.0
Disambiguation5/5

Each tool has a clear, distinct purpose with detailed descriptions and explicit WHEN TO USE / WHEN NOT TO USE guidance. Potential overlaps like send_message vs. send_transactional_confirmation are well-differentiated by idempotency and use case, and compliance tools (check_compliance, screen_sanctions, map_trade_restriction) operate on different scopes without ambiguity.

Naming Consistency5/5

All tool names use lowercase snake_case and follow a consistent verb_noun pattern (call_business, check_quota, find_business, send_message, verify_company_record). Even less standard verbs like lookup, map, and mint follow the same structural convention, and there are no mixed casing styles or inconsistent naming patterns.

Tool Count4/5

With 23 tools, this is slightly above the typical 3-15 range, but the breadth of the server's purpose—covering communication, scheduling, compliance, trade screening, and operational utilities—justifies the count. Each tool addresses a distinct capability area, and the set is not bloated with redundant or trivial functions.

Completeness5/5

The tool surface covers the full lifecycle of the broker's domain: business discovery, booking (check, import, schedule), communication (send, receive, read), compliance (pre-flight checks, sanctions, trade restrictions, company verification), and operational support (quota, health, cost preview, key minting, async status/outcome). There are no obvious dead ends or missing critical operations for the stated purpose.

Resources