Skip to main content
Glama

Compare a service with budget, extras and date

compare_options
Read-onlyIdempotent

START HERE for choosing a service under a budget, with extras, or on a date. Use search_merchants for name/address lookup; use this tool for the service decision. Compare a supported service intent, optional budget/date/neighborhood, strict or nearby geography, and selected add-ons (blow_dry, haircut, toner, shampoo, deep_conditioning, iron_finish, extensions). Returns options, uncertain and excluded service decisions plus separately paginated unresolved_salons when no matching service is established. next_action.booking_url is the direct merchant destination, with link scope and check status. Returns service decisions with per-fact sources/dates, known subtotal including requested/mandatory extras, unresolved charges, explicit conditions, hours conflicts and exact next actions. Starting prices and required consultations never become guaranteed final quotes. Deposit is advance payment, not an added charge. There is no provider-confirmed availability; date-specific results are conditional. Time-of-day, stylist and hair-length requirements are unsupported filters here; retain them for merchant confirmation. Ordering is geographic/alphabetic, not a quality rating. No booking or hold is created. Paginated: limit <= 50, offset; use next_offset across all three result groups.

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_intent": "<service_intent>"
    },
    "name": "compare_options"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoValid YYYY-MM-DD in America/Los_Angeles; not a confirmed appointment
limitNoTotal entries across options/uncertain/excluded; continue with next_offset
salonNoOptional salon slug or ref from search results to compare only that salon.
budgetNoUSD cap for the requested service and selected/mandatory extras. A lower bound is not proof the full price fits.
offsetNo
geographyNostrict by default; nearby requires a neighborhood and explicit permission to include nearby salons.strict
neighborhoodNo
service_intentYescolor, balayage, balayage color, creative color, color consultation, highlights, haircut, mens haircut, womens haircut, wash cut style, or blowout; unsupported intents are errors
selected_addonsNoOnly extras the user requested. Mandatory extras are added automatically; unknown charges are not free.
require_availabilityNoRequire provider-confirmed availability. None exists today; opening hours and candidate times cannot satisfy this.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/closed-world, yet the description adds substantial non-obvious behavior: no booking or hold is created, no provider-confirmed availability exists, date results are conditional, ordering is geographic/alphabetic rather than quality, starting prices never become guaranteed quotes, and deposit is advance payment rather than an added charge.

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-loaded with the decision guidance and the sibling routing, which is the right order. It is dense but largely earns its length; a few sentences overlap ('Returns options, uncertain and excluded service decisions...' followed later by 'Returns service decisions with per-fact sources/dates...') and could be merged.

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?

For a 10-parameter tool with no output schema and no output_schema support, the description covers return shape (options/uncertain/excluded/unresolved_salons), pagination across all three groups via next_offset with limit<=50, and the caveats an agent needs to set user expectations. Nothing essential to correct invocation is 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 80%, so baseline is 3; the description still adds meaning by enumerating the supported service intents and add-on vocabulary, clarifying that budget applies to requested plus mandatory extras, and explaining that geography=nearby requires a neighborhood and explicit permission. It does not, however, re-explain offset beyond the pagination instruction.

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?

States a specific verb+resource ('Compare a supported service intent') with scope qualifiers (budget/date/neighborhood/add-ons), and explicitly tells the agent it is the entry point ('START HERE'). It also draws a hard line against the closest sibling: 'use search_merchants for name/address lookup; use this tool for the service decision.'

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?

Gives an explicit when-to-use ('choosing a service under a budget, with extras, or on a date') and names a sibling alternative plus the condition that selects it over this tool. It also pre-empts misuse by declaring what is NOT supported here (time-of-day, stylist, hair-length) so the agent knows to defer those to merchant confirmation.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources