Skip to main content
Glama

VoiceAssistants

Check a business's hours

get_hours
Read-onlyIdempotent

Answer "is it open now?", "when does it close?" and "is it open on Thanksgiving?" for one business in the VoiceAssistants directory. Returns whether it is open at this moment in its own time zone, today's hours, the full week, and any holiday hours on file. If the business has no hours on file it says so rather than guessing. Pass the id from find_businesses. Read spoken aloud.

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": {
      "id": "<id>"
    },
    "name": "get_hours"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe business id from find_businesses.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

The annotations already declare readOnly/idempotent/non-destructive, so the bar is lower, and the description still adds real behavioral context: results are computed in the business's own time zone, holiday hours may be present, and the tool explicitly reports missing hours instead of guessing. It also tells the agent to read the `spoken` field aloud, a calling convention not encoded anywhere in the schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It leads with the user questions the tool answers, then the payload, then the no-data behavior, then the id source and the spoken-field convention. Four sentences, each carrying distinct information, with no preamble or filler.

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?

There is no output schema, so the description carries the burden of describing returns, and it does so concretely: current open status, today's hours, full week, holiday hours, plus the guarantee of an explicit 'no hours on file' response. Combined with the annotations, an agent can call this correctly without further information.

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 parameter already documents itself as "The business id from find_businesses"; the description's instruction to pass the id from find_businesses merely repeats that. No additional semantics about id format, prefixes, or failure modes on an invalid id are added.

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 states the specific resource and scope — open status, today's hours, weekly hours and holiday hours for a single business in the VoiceAssistants directory — which is far more than a restatement of the name. It does not, however, distinguish itself from the sibling answer_question, which could plausibly handle a spoken 'is it open now?' query, nor from get_business.

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

Usage Guidelines4/5

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

Usage is grounded in concrete caller intents ("is it open now?", "when does it close?", "is it open on Thanksgiving?") and it tells the agent where the required id comes from (find_businesses). It stops short of stating when not to use it or which sibling to prefer for general business details or free-form questions.

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