Skip to main content
Glama
Sign In
clover-mcp

clover-mcp

by SBolivarLoL
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

list_opening_hours

Read-only

Get the merchant's weekly opening hours with per-day time ranges. Ideal for displaying store hours or verifying availability.

Instructions

Return the merchant's opening-hours sets (per-day time ranges). Requires MERCHANT_R.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.7.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, and the description adds a critical auth requirement (MERCHANT_R) beyond the structured data. It also specifies the structure of the return data (per-day time ranges), which helps the agent understand the response format.

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 a single sentence that packs purpose, structure, and permission requirement without fluff. It is front-loaded with the verb.

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?

For a read-only, zero-parameter tool, this description is sufficient: it states the purpose, permission, and basic return structure. The output schema exists to fill in details, so the description need not elaborate further.

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?

There are zero parameters, so the schema is fully covered. The description doesn't need to explain parameters, and the per-day time range detail adds context to the output.

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's function with a specific verb ('Return') and resource ('opening-hours sets'), and details the output ('per-day time ranges'). This distinguishes it from other list_* sibling tools, as none specifically target opening hours.

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 clear context: it should be used when the merchant's opening hours are needed. It doesn't explicitly name alternatives, but the scope is so specific that no alternative is obvious; there are no exclusions.

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

Deploy Server

Other Tools