Skip to main content
Glama
nuxnik

Busy Bar MCP Server

by nuxnik

get_tzlist

Retrieve the complete list of timezones supported by a Busy Bar device, including offsets and abbreviations, to select or verify a timezone before setting it.

Instructions

Retrieve the full list of supported timezones from the Busy Bar device.

This tool queries /api/time/tzlist on the device and returns every timezone
that can be used with the set_timezone functionality (/api/time/timezone POST).

Returns a TimezoneListResponse object containing:
    - list:  list[TimezoneInfo]  — an array of available timezones, each with:
        - name:  str  — human-readable timezone name (e.g., 'America/New_York')
        - offset: str — UTC offset string (e.g., '-05:00', '+05:30')
        - abbr:   str — timezone abbreviation (e.g., 'EST', 'IST')

Use case:
    Browsing the available timezones before choosing one to apply via set_timezone.
    Useful for building a UI dropdown or confirming that a specific named timezone is supported.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

No annotations exist, so the description carries the behavioral burden. It clearly indicates a read-only query operation ('queries', 'returns') and documents the exact endpoint. It also details the return object structure, which provides strong transparency, though it could explicitly state it has no side effects.

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?

The description is well-organized: a one-line summary, endpoint reference, structured return type with field explanations, and a use-case section. Every sentence adds value, and it is appropriately sized for a simple tool.

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?

The description is complete for this tool's complexity. It specifies the endpoint, return object fields, and practical use cases. Even without an output schema, it fully explains the returned timezone list, making the tool self-contained.

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?

With zero parameters, the parameter baseline is 4. The description correctly indicates the tool takes no parameters and focuses on what it returns, so no additional parameter documentation is needed.

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?

The description clearly states a specific action ('Retrieve the full list of supported timezones') targeting a specific resource (the Busy Bar device's /api/time/tzlist). It distinguishes itself from sibling get_timezone by focusing on the list of supported timezones rather than the current timezone.

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

Usage Guidelines5/5

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

The 'Use case' section explicitly explains when to use this tool: browsing timezones before setting one, building a UI dropdown, or confirming support. This provides clear guidance on when to use it versus alternatives like get_timezone.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/nuxnik/busybar-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server