Skip to main content
Glama
Sign In

Ysaere

by com.ysaere.mcp
OverviewDiscussionsAdmin

Find Local Service

frontdoor_find_local_service
Read-only

Find local service businesses (pool cleaning, pool repair, lawn care, landscaping; Florida Gulf Coast to start) from a plain-language request, e.g. "weekly pool cleaning in 34202 under $125/mo, Saturdays". Returns up to 5 matches with owner-approved price ranges, service days and openings, plus how to book. Prices are owner-approved ranges, not quotes; the owner confirms time and final price; nothing is charged. Free. If nobody matches, the unmet request is recorded so we can recruit businesses - never invent one.

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": {
      "request": "<request>"
    },
    "name": "frontdoor_find_local_service"
  }
}

Input Schema

NameRequiredDescriptionDefault
zipNo5-digit ZIP where the service is needed (recommended if not in the request text).
unitNoUnit for max_price_usd: per_month (recurring), per_visit, or per_job (one-time).
requestYesWhat the person needs, in plain language, e.g. "weekly pool cleaning in 34202 under $125/mo, Saturdays". Do not include the person's name, phone, email or street address.
max_price_usdNoMaximum the person wants to pay in US dollars, in the unit given below.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

The annotations already declare readOnlyHint=true and openWorldHint=true. The description adds real behavior: at most 5 matches, owner-approved price ranges rather than quotes, the owner confirming time and final price, no charge, and a note that the tool records unmatched requests so businesses can be recruited. That recording is a short-lived side effect and the only minor tension with readOnlyHint, but it is disclosed clearly rather than hidden.

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 definition leads with what the tool does, then covers pricing and a fallback. It is dense but every clause adds useful content. The pricing disclaimers could be compressed slightly.

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?

There is no output schema, so the description must explain the return value; it does this well (up to 5 matches, price ranges, service days, openings, booking path). With free pricing, a no-charge guarantee, and a no-invention rule, an agent can call this tool and interpret the results without making further assumptions.

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?

The schema describes all 4 parameters at 100%, so the description only needs to reinforce meaning. The embedded example request illustrates how the request text can carry a ZIP, price, unit, and day, but it adds no new constraint or format guidance beyond the schema.

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 clearly states a specific verb and resource (find local service businesses) and limits the scope (pool, lawn, landscaping; Florida Gulf Coast). A concrete example request lets an agent distinguish this discovery tool from booking or business-detail tools.

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?

The description makes the trigger explicit: a plain-language service request with optional ZIP, budget, unit, and days. It also explains the fallback when nobody matches, but it does not name the sibling tools (for example, request_booking or get_business) or say when one should use those instead of this one.

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

All Ysaere 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