Skip to main content
Glama
Crawlora MCP

Crawlora MCP

Official

booksy_treatment_hints

Find Booksy treatment IDs by querying service names such as haircut or nails; returns matching treatments and suggested businesses to seed treatment-based business searches.

Instructions

Discover Booksy treatment ids for a query. Returns the treatments and businesses Booksy's (booksy.com) app API suggests for one search text, with each treatment's integer id, name, slug and type, and each suggested business's id, name, slug, web path token and address. This is the discovery step for the treatment parameter of booksy-businesses, and it is the only treatment-id surface the app API exposes. It is query-driven, not a complete value space: the response says query_driven=true because the upstream returns only what the query matches, and no route found returns the full treatment taxonomy, so a treatment id outside these answers can exist. Prefer seeding it with the service name you want (haircut, braids, nails, massage). A query that matches nothing answers an empty suggestions array rather than an error; a blank query is rejected.

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": {
      "query": "<query>"
    },
    "name": "booksy_treatment_hints"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesSearch text that seeds the hint lookup
countryNoMarket host

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

TDQS

A4.8/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does so: it discloses the query_driven=true response flag, the empty-suggestions-not-error behavior, blank-query rejection, and the incompleteness caveat. Real error semantics and limits are visible without calling the tool.

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?

The core purpose and routing to booksy-businesses are front-loaded, and each sentence adds a distinct fact (return shape, routing, completeness caveat, seeding advice, error behavior). Sentences are dense and slightly 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?

No output schema exists, and the description compensates by enumerating the returned treatment and business fields. For a two-parameter read tool with no annotations, it covers purpose, routing, edge cases, and output shape with nothing an agent needs missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning: the query should be seeded with a service name and example values are given, plus the blank-query behavior. The country parameter's semantics are left entirely to the schema's 'Market host' enum, which is the only gap.

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 opens with a specific verb-resource pair ('Discover Booksy treatment ids for a query') and enumerates the returned fields for treatments and businesses. It also distinguishes itself from siblings by naming booksy-businesses and its treatment parameter, so an agent can see the relationship without opening either schema.

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?

It states the tool is the discovery step feeding the treatment parameter of booksy-businesses and is 'the only treatment-id surface the app API exposes', which routes the agent clearly. It also says what to seed it with ('Prefer seeding it with the service name you want (haircut, braids, nails, massage)') and warns against treating it as an enumeration because no route returns the full taxonomy.

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