Skip to main content
Glama

Find open times

find_open_times
Read-only

Ryan's open start times for this job (they depend on how long it takes). Use a start_time exactly as given.

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": "find_open_times"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoHow many days to look at (default 7).
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%).
from_dateNoFirst day to look at, YYYY-MM-DD (default today).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/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 safety is covered. The description adds genuine behavioral context: availability is duration-dependent and returned start times must be used verbatim rather than rounded or reformatted. It says nothing about how many slots come back, timezone, or how far ahead availability is offered.

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?

Two short sentences with no filler, and the key point (duration-dependent availability) is front-loaded. 'Ryan's' and 'this job' are slightly cryptic without context, but nothing is wasted.

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

Completeness3/5

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

With six parameters, three enums, and no output schema, the description should say more about what comes back. It implies a list of open start slots but never states the format, timezone, or typical count, which matters since there is no output schema to fall back on.

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 coverage is 100% with rich enum descriptions for service, vehicle, condition, and add_ons, so the schema carries the parameter burden. The description adds no parameter meaning, and it references 'start_time,' which is not even an input field, which could momentarily confuse an agent mapping inputs.

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 makes clear the tool returns available start times for a given job, and adds that the returned slots depend on job duration. It lacks an explicit verb and does not distinguish itself from siblings like get_quote or request_booking, but an agent can still tell what it does 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 Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no statement of when to call this versus get_quote, request_booking, or change_booking_time. The only guidance, 'Use a start_time exactly as given,' is an instruction about consuming the output, not about tool selection, so an agent must infer that this is the pre-booking availability lookup.

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