Skip to main content
Glama
adrighem

Domoticz MCP Server

by adrighem
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

get_sun_times

Retrieve sunrise, sunset, and twilight times based on your home coordinates to automate lighting or scheduling.

Instructions

Get sun times (sunrise, sunset, twilight) based on home coordinates.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • src/domoticz_mcp/server.py:894-898 (handler)
    The get_sun_times tool handler function. It makes an HTTP GET request to the Domoticz API endpoint 'getsunrisenset' to retrieve sun times (sunrise, sunset, twilight) based on home coordinates.
    async def get_sun_times() -> str:
    """Get sun times (sunrise, sunset, twilight) based on home coordinates."""
    async with create_client() as client:
        response = await _do_request(client, "GET", f"{DOMOTICZ_API_URL}?type=command¶m=getsunrisenset")
        return response.text
  • src/domoticz_mcp/server.py:894-894 (registration)
    The tool is registered with the MCP server via the @mcp.tool() decorator on line 893, which is how FastMCP registers functions as tools.
    async def get_sun_times() -> str:

Tool Definition Quality

B3.3/5.0
Behavior2/5

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

No annotations provided, so description must fully disclose behavior. It mentions 'based on home coordinates' but does not specify if coordinates are configurable, what happens if unset, or the exact return structure beyond naming three fields.

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?

Single sentence with 10 words, no redundancy, front-loaded with action and result.

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?

Given no input parameters and presence of output schema, description is mostly adequate. However, it lacks clarity on the dependency on home coordinates and no mention of error conditions.

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?

Input schema has zero parameters with 100% coverage, so baseline is 3. Description adds context about using home coordinates, which is useful but still vague.

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 the tool retrieves sun times (sunrise, sunset, twilight) based on home coordinates. It uniquely identifies the resource and is distinct from siblings like get_all_devices or get_system_status.

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

Usage Guidelines2/5

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

No guidance on when to use this tool vs alternatives, no prerequisites mentioned. It does not explain if home coordinates must be configured first or how the tool handles missing data.

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/adrighem/domoticz-mcp'

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