ServiceBuddy Auto Repair Savings
Server Details
Auto repair price benchmarks and current service deals for any US ZIP. No account required.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Average 4.5/5 across 1 of 1 tools scored.
Only one tool exists, so there is zero ambiguity about which tool to select. The tool's description is clear about its single purpose.
The single tool name 'get_evaluated_savings' follows a clear verb_noun pattern, and with only one tool, consistency is trivial.
The server provides only one tool for a domain that could benefit from separate tools for pricing lookup, coupon discovery, and quote comparison. This feels under-scoped for the broad set of services and features described.
The tool covers the core needs: typical pricing, best discounts, effective price, and optional quote comparison. Minor gaps exist (e.g., shop listing, specific negotiation handling), but the surface is largely complete for its stated purpose.
Available Tools
1 toolget_evaluated_savingsFind Best Auto Service DealARead-onlyIdempotentInspect
Find the best current auto-service deal near a US ZIP or metro and see what you'd actually pay. Returns the local typical price for the service (oil change, brakes, battery, diagnostic, coolant flush, tire rotation, tires), the best current coupon, discount, or rebate, and the net out-of-pocket "effective price" after discounts and rebates, with caveats. Optionally compares against a shop quote the user already has. Use when someone asks what a repair should cost, whether a quote is fair, or where to find a coupon. US only; 16 major metros are priced locally, other ZIPs use national averages.
| Name | Required | Description | Default |
|---|---|---|---|
| zip | No | 5-digit US ZIP, e.g. "11205". Give zip or city for local pricing; omit both for national averages. | |
| city | No | Metro slug, e.g. "new-york-city", "los-angeles", "houston". Overrides zip. | |
| shop_name | No | Shop or chain the user mentioned, e.g. "Jiffy Lube", to prioritise that brand's deals. | |
| quoted_price | No | A quote the user already has, in USD, e.g. 119. Enables "is this quote fair?" comparison. | |
| service_variant | No | Oil type (oil_change only). Omit to evaluate each offer on its own stated oil type. | |
| service_category | No | Service to price. | oil_change |
Output Schema
| Name | Required | Description |
|---|---|---|
| cached | Yes | True if served from the 12-hour deal cache. |
| summary | Yes | Plain-English summary of the local price and best deal. |
| benchmark | Yes | |
| best_match | Yes | Highest-savings offer, or null if none found. |
| offers_count | Yes |
Tool Definition Quality
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations provide readOnlyHint, openWorldHint, idempotentHint, and destructiveHint, so the safe, read-only nature is already declared. The description adds useful behavior: it returns typical price, best coupon, effective price with caveats, and optionally compares against a quote. It doesn't go into details like data freshness, but given strong annotations, this is solid.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single well-structured paragraph that starts with the main purpose, then details the returns and usage context. It is concise, though a bit long; every sentence adds useful information, but a slight restructuring could make it even more scannable.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The tool returns an effective price with caveats, and there is an output schema (not shown) that likely documents the return structure. The description covers input semantics, including service types and the quote comparison, and notes US-only and local coverage. It's complete for agent use, though it doesn't mention error conditions, but these are not critical.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, and the description adds value by explaining the overarching logic: zip/city for local pricing, shop_name for brand priority, quoted_price for comparison, and service_variant for oil type. This goes beyond schema descriptions, especially for the interplay between zip and city and the commas in effective price.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool's function: find the best auto-service deal near a US ZIP or metro and compute the effective price after discounts. It specifies available service types and the comparison option. The title reinforces this, and there are no siblings that could cause confusion.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description explicitly states when to use the tool: 'Use when someone asks what a repair should cost, whether a quote is fair, or where to find a coupon.' It also notes US-only and explains the distinction between local pricing for 16 metros and national averages for other ZIPs, providing clear context without naming alternatives.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceScrapes real-time gas prices from GasBuddy.com to find the cheapest fuel in any US city or zip code.1MIT

costkits-mcpofficial
AlicenseAqualityAmaintenanceProvides live US healthcare cost data including procedure cost estimates, provider pricing, insurance coverage rules, and medical bill analysis using real hospital transparency and CMS data.12120MIT- AlicenseNot gradedqualityCmaintenanceProvides AI agents with authoritative OEM automotive repair data including part numbers, torque specs, fluid capacities, and service procedures for vehicles 1982-2013 across 80+ makes, sourced from factory service manuals.MIT
- AlicenseNot gradedqualityDmaintenanceProvides comprehensive vehicle reports by aggregating data from multiple public sources to decode VINs, check recalls, and view safety ratings. It enables users to validate VINs locally and retrieve technical specifications, fuel economy, and vehicle photos without requiring API keys.18MIT