Skip to main content
Glama
Lucacelli B2B MCP Server

Lucacelli B2B MCP Server

Restaurant Toast POS, OpenTable & Delivery Spy

find_restaurant_toast_opentable_leads
Read-onlyIdempotent

Detect Toast POS, Square, OpenTable, Resy, DoorDash, UberEats, and contact emails on restaurant websites from domain lists to enrich B2B restaurant leads.

Instructions

Detect Toast POS, Square, OpenTable, Resy, DoorDash, UberEats, and contact emails across restaurant websites ($0.50/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_restaurant_toast_opentable_leads"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainsYesRestaurant domains to enrich

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds genuine value with pricing ('$0.50/1k'), which lets an agent budget large domain batches, but it says nothing about rate limits, partial-match behavior, or what happens on unreachable domains.

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 first and closes with the cost signal. No filler, no restatement of the title, and every clause carries information.

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?

For a one-parameter enrichment tool with no output schema, the enumerated signal list effectively communicates what comes back per domain, which is the key missing piece in most definitions. A brief note on output shape or failure handling would make it complete.

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?

Only one parameter exists and schema coverage is 100%, so the schema fully documents 'domains' as an array of restaurant domains to enrich. The description reinforces the scope ('across restaurant websites') but adds no format, batching, or limit detail beyond the schema, which is the expected baseline here.

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 uses a specific verb ('Detect') and enumerates the exact signals it looks for (Toast POS, Square, OpenTable, Resy, DoorDash, UberEats, contact emails) scoped to restaurant websites. An agent knows what the tool produces, though it does not explicitly contrast itself with the sibling lead-scraping tools for other verticals.

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 only implied: the vertical ('restaurant websites') and the signal list suggest this is for tech-stack enrichment of restaurant domains, not general lead generation. There is no explicit when-to-use, when-not-to-use, or named alternative guidance.

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