Skip to main content
Glama

Get hours and emergency availability

get_hours_and_emergency
Read-onlyIdempotent

AtlantFlow's hours: whether regular service hours are open at a given moment (default now), whether the $149 emergency call fee applies at that time, and the rules for Sundays and nights. Calls are answered 24/7.

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

Input Schema

NameRequiredDescriptionDefault
datetimeNoOptional local time (America/New_York) as ISO 8601, e.g. '2026-11-01T19:30'. Omit for right now.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already establish readOnly, idempotent, non-destructive, non-open-world behavior, so the description's job is to add context — and it does, disclosing the specific facts returned (open status, a concrete $149 fee determination, weekend/night rules) and the reassurance that calls are answered 24/7 regardless of posted hours. It stops short of describing response shape or edge cases like holidays.

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, front-loaded with the resource and the three returned facts; the 24/7 note is separated so it does not clutter the main clause. The colon-list construction is slightly dense but every clause carries information.

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

Completeness4/5

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

With no output schema, the description carries the burden of explaining what comes back, and it names all three logical return elements plus the practical 24/7 caveat. Only minor gaps remain — no mention of holiday handling or the shape/units of the response.

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% and the single datetime parameter already documents ISO 8601 format, the America/New_York timezone, and the omit-for-now default. The description reinforces 'default now' and 'at a given moment' but adds no new syntax or format meaning, so the baseline of 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 specific resource (AtlantFlow's hours) and enumerates exactly what is returned: open/closed status at a moment, whether the $149 emergency fee applies, and Sunday/night rules. That is far more informative than the title, though it never differentiates itself from schedule-adjacent siblings like get_booking_options or get_company_info.

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: '(default now)' and 'at a given moment' tell the agent to pass a time when asking about a specific moment, and the 'Calls are answered 24/7' line hints at when the hours question is moot. There is no explicit when-to-use/when-not-to-use guidance and no named alternative tool.

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