Skip to main content
Glama
Sign In
SetLuca

SetLuca

Official
by setluca
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get a booking provider

luca_bookings_providers_get
Read-onlyIdempotent

Retrieve the event types and calendars for a connected booking provider account, with optional workspace overrides. Use it to inspect available scheduling options.

Instructions

List the event types and calendars in one connected provider account.

Luca operation: GET /api/bookings/providers/{provider} Required scopes: bookings:read Required OAuth scope: luca:read; data sensitivity: redacted Does not require idempotency. Use workspaceId or workspaceSlug to override the default workspace configured by environment.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "provider": "<provider>"
    },
    "name": "luca_bookings_providers_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
providerYes
workspaceIdNoOptional Luca workspace id override.
workspaceSlugNoOptional Luca workspace slug override.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), and the description adds value beyond them: required scopes (bookings:read, luca:read), 'data sensitivity: redacted' for the returned data, and the workspace-override behavior. 'Does not require idempotency' is not a contradiction of idempotentHint=true (it means no idempotency key is needed), though the phrasing is loose.

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?

Purpose is front-loaded in the first sentence and the operational metadata is compressed into short labeled lines. There is mild boilerplate redundancy between 'Required scopes: bookings:read' and 'Required OAuth scope: luca:read', but nothing is padded.

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?

An output schema exists, so return-value shape needn't be documented, and annotations carry the safety profile. Combined with scopes, sensitivity level, and workspace-override semantics, the agent has enough to invoke it correctly; only the lack of routing guidance relative to sibling list tools leaves a gap.

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 67%: both workspace parameters carry their own descriptions, while the required `provider` enum (manual, calendly, cal_com, google_calendar, iclosed, gohighlevel) is undocumented. The description explains the meaning of the workspace override ('the default workspace configured by environment') but adds nothing about the provider enum values.

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

Purpose4/5

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

The description names a concrete resource ('the event types and calendars in one connected provider account'), so an agent knows what data comes back. It doesn't distinguish itself from sibling readers such as luca_bookings_providers_list, luca_bookings_types_list, or luca_bookings_calendars_list, and the 'list' framing sits awkwardly against the title 'Get a booking provider'.

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?

The only usage instruction is 'Use workspaceId or workspaceSlug to override the default workspace configured by environment,' which is real but narrow guidance. Nothing tells the agent when to call this instead of the providers/types/calendars list tools, so selection guidance is only implied.

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

Deploy Server

Other Tools