Skip to main content
Glama
Sign In

Bay Area Mobile Dog Wash Booking

by io.github.asarogers
OverviewDiscussionsAdmin

get_quote

Compute the exact total for a wash: dog size + chosen add-ons, minus the first-wash discount, plus the extended-area travel fee when it applies. Use this to state a confident, exact price instead of doing the math yourself.

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": {
      "dog_size": "<dog_size>"
    },
    "name": "get_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
addonsNoAdd-ons the customer wants, if any.
dog_sizeYesDog size tier (Small <20 lbs, Medium 20–60, Large 60–100, XL/Giant 100+).
first_washNotrue if this is a first-time customer — applies the WASH10 ($10 off) discount.
address_or_cityNoWhere the van comes, so the extended-area travel fee is included when it applies.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the burden and discloses the pricing formula: dog size plus add-ons, minus first-wash discount, plus extended-area travel fee when applicable. It does not explain return structure beyond 'exact total' or edge cases, but the core behavior is transparent.

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?

Two efficient sentences: the formula is front-loaded, followed by the usage instruction. There is no redundant or filler language.

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 four-parameter quote tool with full schema coverage and no output schema, the description is nearly complete: it explains the calculation and identifies the return as an exact total. It could mention whether a breakdown is returned, but no major usage gap remains.

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 100%, so the parameters are already documented. The description adds value by explaining how dog_size, addons, first_wash, and address_or_city combine into the final price, especially the conditional travel fee.

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, 'Compute,' and a clear resource, 'exact total for a wash,' with the cost components named. It is distinct from siblings like book_wash or get_services, though it does not explicitly name those alternatives.

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?

It gives clear usage context: 'Use this to state a confident, exact price instead of doing the math yourself.' It does not specify when not to use it or explicitly route to check_service_area or get_services.

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

All Bay Area Mobile Dog Wash Booking 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