Skip to main content
Glama

get_business_hours

Opus Lumière session hours by weekday, with timezone (Europe/London) - overall and for each kind of photoshoot (outdoor, studio, at home). Sessions are by appointment - confirm a real slot with check_availability.

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_business_hours"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and provides meaningful behavioral context: timezone Europe/London, breakdown by weekday and by photoshoot type, and appointment-only semantics. It does not describe return format, permissions, or rate limits, but for a zero-parameter informational read tool this is reasonably complete.

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?

Two tightly written sentences with no waste. The core scope is front-loaded, and the second sentence adds actionable routing guidance without bloat.

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?

Given no output schema and no parameters, the description adequately explains what information is returned (hours by weekday, by photoshoot type, with timezone) and how it relates to check_availability. A minor gap is the absence of explicit return shape or format, but the essential context is present.

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?

The tool has zero parameters, so baseline is 4. The description adds useful context about the informational scope (weekday, timezone, photoshoot types) even though there are no parameters to document.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific resource and scope: 'Opus Lumière session hours by weekday, with timezone (Europe/London) - overall and for each kind of photoshoot (outdoor, studio, at home).' This clearly distinguishes it from sibling tools, especially check_availability, which it explicitly names for real slot confirmation.

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?

The description gives a clear usage context: 'Sessions are by appointment - confirm a real slot with check_availability.' It routes the agent to the correct alternative for availability, though it does not explicitly state when not to use this tool or other exclusions.

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