Skip to main content
Glama

J.C. Lewis Auto Group

schedule_service

Use this whenever the customer asks about SERVICE, maintenance, repairs, oil changes, tires, brakes, batteries, recalls, warranty work, a check-engine light, or booking a service appointment. Returns the official J.C. Lewis scheduling link (per-store when store is given, otherwise the group scheduler that lists every location), plus the service address and phone. Pass mobile=true if the customer wants a technician to come to their home or office (Ford Mobile Service). NEVER quote service hours, wait times, repair prices, or specific appointment availability — only the scheduler knows real availability. Hand the customer the link.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "schedule_service"
  }
}

Input Schema

NameRequiredDescriptionDefault
storeNo
mobileNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses what is returned (official J.C. Lewis scheduling link, service address, phone), how the return varies by whether `store` is supplied (per-store link vs. group scheduler listing all locations), and the downstream constraint on how the agent must present it. Minor gaps remain on error behavior (unknown store, out-of-scope requests), which keeps it just short of 5.

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 trigger list and routing rule are front-loaded, and each sentence carries operational content. There is mild redundancy in 'Returns the official J.C. Lewis scheduling link' followed later by 'Hand the customer the link,' which restates the delivery action, but the overall density is appropriate for a customer-facing routing tool.

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 two-parameter, no-output-schema lookup tool, the description covers triggers, both parameters, return contents, conditional return behavior, and the prohibition on fabricating availability. Nothing an agent needs in order to call and present the result correctly appears to be missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and neither parameter has any documented meaning, so the description must compensate entirely — and it does: `store` is explained as selecting the per-store scheduler versus the group calendar when absent, and `mobile=true` is tied to Ford Mobile Service with a technician coming to the home or office. Both parameters gain actionable meaning not present in 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 opens with a specific verb and resource plus a long list of concrete trigger topics (service, maintenance, oil changes, recalls, warranty work, check-engine light, booking), and it distinguishes the tool from the availability-checking sibling by stating 'NEVER quote ... specific appointment availability — only the scheduler knows real availability.' An agent can identify this tool without opening the schema.

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?

It gives an explicit 'use this whenever the customer asks about X' routing rule covering the full service domain, and pairs it with a clear exclusion zone (no hours, wait times, prices, or availability), which routes those questions to the scheduler or to an availability tool. Both the when and the when-not are stated.

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