Skip to main content
Glama

Inescapable Detail

Open days and times

find_open_times
Read-only

Open visit times in the next days (Jacksonville time). Mornings are 7 to 11 AM, afternoons 12:30 to 5 PM; Monday, Wednesday and Friday are mornings only; Saturday is closed. Set whole_day true for The Full Package: only days with the whole day open are listed. More than one car at one address: text David.

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

Input Schema

NameRequiredDescriptionDefault
daysNoHow many days ahead to look (default 14).
whole_dayNoTrue for The Full Package or more than one car.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Read-only safety is already covered by readOnlyHint, yet the description still adds substantial domain behavior: the morning window 7–11 AM, afternoon 12:30–5 PM, the Mon/Wed/Fri mornings-only rule, Saturday closure, and that whole_day=true filters to fully-open days only. It does not say whether results are ordered, how many entries come back, or what the response shape looks like.

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?

Front-loaded with the tool's purpose, then the operating constraints, then the escalation note. Every sentence carries information, though the block of schedule rules reads as a dense run-on and could be punctuated more cleanly.

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?

With two optional parameters, full schema coverage, and no output schema, the description supplies exactly the domain rules an agent needs to call it and interpret the result. The 14-day default is documented in the schema, so nothing material is missing.

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 baseline is 3, but the description earns credit by clarifying whole_day beyond the schema's terse 'True for The Full Package or more than one car' — it explains the consequence (only fully-open days are listed). The days parameter's meaning lives in the schema and is not restated.

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?

States a specific verb and resource — 'Open visit times in the next days' — with a timezone qualifier (Jacksonville time). An agent can distinguish it from book_visit (which would reserve a slot) and get_services without opening either schema, though no sibling is named explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

Usage is implied rather than stated: this is the availability lookup that precedes booking, and the closing rules (Saturday closed, mornings-only days) tell the agent what will come back. There is no explicit 'call this before book_visit' instruction, and the 'more than one car: text David' escalation is an out-of-band caveat rather than routing guidance.

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