Skip to main content
Glama

Get a price

get_quote
Read-only

The price for a service, with the plan prices (every 2 or 4 weeks) to offer once. Quotes are the price; Ryan confirms by text.

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": "<service>",
      "vehicle": "<vehicle>"
    },
    "name": "get_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
add_onsNoOptional extras: pet-hair = Pet hair removal (+$35; with interior/full); shampoo = Carpet & seat shampoo (+$60; with interior/full); odor = Odor elimination (+$50; with interior/full); headlights = Headlight restoration (+$60; with wash/interior/exterior/full); engine = Engine bay cleaning (+$45; with exterior/full).
serviceYesService: wash = Maintenance wash (from $79); interior = Interior detail (from $169); exterior = Exterior detail (from $149); full = Full detail (from $249); ceramic = Ceramic coating (from $899, one-time only).
vehicleYesVehicle size: sedan = Sedan / coupe; suv = SUV / crossover; truck = Truck; xl = 3-row / van / XL.
conditionNoHow it looks right now (first visit only; default lived): fresh = Basically clean; lived = Lived-in; kids = Kid-tested (+15%); dog = The dog's car now (+30%); yikes = We don't judge (+50%).
how_oftenNoonetime (default), biweekly = every 2 weeks (15% off each visit), monthly = every 4 weeks (10% off).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds that a quote is not a commitment ('Ryan confirms by text') and that quoted prices are authoritative, but leaves unstated whether quoted amounts include add-ons/discounts, whether they are final or 'from' estimates, and what the caller should do with the plan prices.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

At two short sentences it is compact and roughly front-loaded on the price concept. However the second sentence is cryptic internal jargon ('Ryan confirms by text') that costs the reader effort without delivering usable guidance, and the first sentence crams two ideas (base quote and plan pricing) into an unclear construction.

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

Completeness2/5

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

This is a five-parameter, four-enum computation tool with no output schema, so the description is the only place to explain what comes back. It never indicates whether the result is a single total or a breakdown per add-on and discount tier, nor how the 'from $' base prices interact with condition multipliers. For a pricing tool whose output shape matters to the caller, that is a material gap.

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% and all four enum parameters document their own pricing impact (base prices, +15%/+30%/+50% condition modifiers, 15%/10% recurring discounts), so the schema does the heavy lifting. The description only gestures at the how_often dimension ('every 2 or 4 weeks') without adding syntax or interaction rules the schema lacks, so this lands at the baseline.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description conveys the resource (the price for a service) and adds that plan prices for 2- or 4-week recurring visits are included, which an agent can map to get_quote vs get_booking. But it opens with a noun phrase rather than a verb, never says it computes/quotes a price from the supplied parameters, and the closing line 'Quotes are the price; Ryan confirms by text' is internal shorthand that muddies rather than sharpens the purpose.

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?

'with the plan prices (every 2 or 4 weeks) to offer once' hints at the scenario of presenting a recurring-plan price, which is weak use-case framing. There is no explicit when-to-use, no when-not, and no comparison to siblings like find_open_times or get_booking that an agent would naturally weigh when a customer asks about cost.

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