Skip to main content
Glama

Caelara Labs Global Locale

business_hours_calc

Is a location open right now (or at a given instant) and when does it next open or close

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": {
      "tz": "<tz>"
    },
    "name": "business_hours_calc"
  }
}

Input Schema

NameRequiredDescriptionDefault
atNoISO 8601 instant to evaluate (default now)
tzYesIANA timezone of the business
endNoClosing time HH:MM (default 17:00)
daysNoComma list of open weekdays, 0=Sunday..6=Saturday (default 1,2,3,4,5)
startNoOpening time HH:MM (default 09:00)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. It usefully discloses the two outputs (current open state and next open/close), which partially compensates for the missing output schema. However, it never states the crucial behavioral fact that the opening schedule is not looked up but must be passed in via start/end/days, nor does it address holiday handling, DST edge cases, or behavior when the instant falls outside the configured week.

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?

A single tightly written sentence with the core capability front-loaded and no filler. The parenthetical is slightly clumsy but it carries real information about the optional evaluation instant.

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 five parameters, one required, no output schema and no annotations, the description covers what the tool returns but leaves the data-source model implicit and says nothing about week-boundary or holiday behavior. It is adequate to attempt a call but not complete enough to predict results in edge cases.

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 description coverage is 100% and every parameter carries a description plus an explicit default, so the schema does the heavy lifting. The description adds no format, constraint, or interaction detail beyond the schema (e.g. that start/end are interpreted in the supplied tz). Baseline 3 applies.

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 names a concrete capability: determining whether a place is open at the current or a specified instant, plus the next open/close transition. That distinguishes it from every listed sibling (timezone_converter, public_holiday_lookup, global_scheduling_composite). It falls short of 5 because 'a location' implies an entity lookup, while the schema actually requires the caller to supply the schedule (tz, start, end, days) 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?

The parenthetical '(or at a given instant)' implies the two usage modes (now vs. a specific timestamp), but there is no explicit when-to-use statement and no comparison to potential alternatives such as global_scheduling_composite or public_holiday_lookup. The agent must infer the boundary cases, notably how this interacts with holiday lookups.

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