Skip to main content
Glama
Lucacelli B2B MCP Server

Lucacelli B2B MCP Server

Salon, MedSpa & Fitness Mindbody/Vagaro Spy

find_salon_medspa_mindbody_leads
Read-onlyIdempotent

Detect Mindbody, Vagaro, Boulevard, Fresha, and Zenoti usage plus owner contact leads for salons, medspas, and fitness studios from supplied domains.

Instructions

Detect Mindbody, Vagaro, Boulevard, Fresha, Zenoti, and owner contact leads across salons, spas, and fitness studios ($0.80/1k).

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": {
      "domains": "<domains>"
    },
    "name": "find_salon_medspa_mindbody_leads"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainsYesSalon/MedSpa/Fitness studio domains

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds genuinely new context: the specific platforms detected, that owner contacts are returned, and the price ($0.80/1k). It does not cover batch size limits, behavior on unrecognized domains, or what the result set looks like.

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?

A single front-loaded sentence that names the detection targets, the verticals, the deliverable, and the price with zero filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema and only one parameter, the description should say more about what a 'lead' record contains and how many domains can be submitted per call. It names owner contacts and the detected platforms, which is helpful, but leaves the return shape and any input limits unstated.

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% for the single 'domains' array, so the schema already explains the input. The description adds no syntax, format, or batching detail beyond what the schema states, which is the expected baseline for a fully documented one-parameter tool.

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 gives a specific verb ('Detect') plus the exact resources targeted: Mindbody, Vagaro, Boulevard, Fresha, Zenoti, and owner contacts across salons, spas, and fitness studios. That is far more specific than a generic lead-scraper, though it never explicitly contrasts itself with the similarly shaped find_dental_medical_clinic_leads or scrape_google_maps_leads siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use or when-not-to-use guidance, and no alternatives are named. An agent must infer from the vertical keywords alone that this is the right tool for salon/spa/fitness prospecting rather than the dental/medical or restaurant siblings.

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