Skip to main content
Glama
Sign In

Lokuli: book local pros and get prices

by com.lokuli
OverviewDiscussionsAdmin

Get open appointment times

get_available_times
Read-onlyIdempotent

Open times for one service at a business, from the business's live Lokuli calendar (the same one its page and apps use). Returns each open slot's start time (ISO) and a label in the business's time zone.

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": {
      "business": "<business>",
      "service_id": "<service_id>"
    },
    "name": "get_available_times"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoFirst day to check, YYYY-MM-DD (default: today)
daysNoHow many days from date (default 3)
businessYesThe business slug or lokuli.com/shop/... link
staff_idNoOptional team member id, to see only their times
service_idYesThe id of one of the business's services

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / service_id / description
      Previous value: -"A service id from get_business"New value: +"The id of one of the business's services"
    • changedInput schema / properties / staff_id / description
      Previous value: -"Optional team member id from get_business, to see only their times"New value: +"Optional team member id, to see only their times"
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, and non-destructive, so the safety profile is covered. The description adds real value beyond that by naming the data source ('the business's live Lokuli calendar, the same one its page and apps use'), which tells the agent the results are authoritative and real-time, not cached.

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?

Two tight sentences, front-loaded with the core purpose and followed by the return shape. No filler, no repetition of the title or annotations.

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?

There is no output schema, and the description compensates by explaining the return payload: each slot's ISO start time and a timezone-correct label. Combined with fully documented parameters, this is close to complete; only edge cases such as an empty availability result are unaddressed.

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 all five parameters including defaults for date and days are already documented. The description only restates that the query is scoped to one service at one business, adding no syntax, format, or edge-case meaning beyond the schema.

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 concrete verb and resource: retrieve open appointment times for one service at one business. The scope (single service, single business) is precise enough that an agent can distinguish it from sibling reads like get_business or find_businesses, though it never names the write-side sibling book_appointment as its counterpart.

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: 'Open times for one service at a business' tells the agent the preconditions (business + service_id) but gives no explicit when-to-use, when-not-to-use, or alternatives. Nothing says to call book_appointment afterward or to use check_coverage first.

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

All Lokuli: book local pros and get prices toolsInspect
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