Lokuli: book local pros and get prices

Get prices from local pros

request_quotes

Has Lokuli phone local service businesses near a US zip code (anywhere in the US) to ask whether they can do a job at the day and time the user wants, and what they'd charge. Lokuli first texts the user a confirmation link; calls start only after they tap it, and prices come back to them by text. Calls go out Monday–Saturday, 11am–6pm local time; a request made outside those hours waits for the next opening. Requires the service, the 5-digit zip, the day and time, and the user's US mobile number. Free for the user. A service that starts with the word "test" (for example "test house cleaning") sends the text and link but calls no business.

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": {
      "service": "<service>",
      "zip": "<zip>",
      "date": "<date>",
      "time": "<time>",
      "phone": "<phone>"
    },
    "name": "request_quotes"
  }
}

Input Schema

Name	Required	Description
`zip`	Yes	5-digit zip code where the service is needed
`date`	Yes	The day they want, YYYY-MM-DD (today through 60 days ahead)
`name`	No	The user's first name (optional)
`time`	Yes	The time they want that day, like "10:00 AM" or "14:30"
`phone`	Yes	The user's US mobile number; the confirmation link and the prices are texted here
`details`	No	Anything a shop needs to quote: size, make/model, problem (optional)
`service`	Yes	What they need, in plain words: "house cleaning", "brake repair", "plumber for a leaking water heater"
`business`	No	Optional: the slug of a business to call first, then nearby pros

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 1, 2026

changedInput schema / properties / business / description

Previous value: -"Optional: a business slug from find_businesses to call first, then nearby pros"New value: +"Optional: the slug of a business to call first, then nearby pros"

First observedNov 1, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Goes well beyond the annotations: the user must tap a texted confirmation link before any call happens, prices return by text rather than in the response, calls only go out Mon–Sat 11am–6pm local and queue otherwise, and the request is free to the user. It also discloses a non-obvious edge case — a service string starting with "test" sends the link but calls no business — which prevents accidental real-world side effects.

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-loads what the tool does before the operational caveats, and each sentence carries a distinct fact (confirmation flow, hours, pricing, test mode). It runs long, but there is no filler to cut.

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 correctly explains that results arrive as a text to the user rather than as return data, and it covers timing, cost, required inputs, and the test-mode escape hatch. 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 coverage is 100%, so the schema already documents all eight parameters including formats. The description reinforces the required set and adds one semantic rule (the "test" prefix on service), but contributes little else 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?

Opens with a concrete verb+resource: it phones local service businesses near a US zip to ask if they can do the job and what they'd charge. That is clearly distinct from siblings like find_businesses (browse listings) and check_coverage (availability of service area).

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 states the prerequisites (service, 5-digit zip, day and time, US mobile number) and the operating-hours window that governs when a request actually goes out. It never explicitly routes the agent to or away from siblings such as find_businesses or get_available_times, so the alternatives comparison is absent.

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 tools Inspect

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

Need Help?