Skip to main content
Glama

Honeyfield Marketing MCP

Business Profile: Manage hours

gbp_manage_hours
Destructive

Reguläre/Sonderöffnungszeiten setzen (Frische-Signal). regular_hours: [{open_day:MONDAY..SUNDAY, open_time:'HH:MM', close_time:'HH:MM', close_day (optional, für Zeiten über Mitternacht)}] — ERSETZT alle regulären Zeiten, immer alle Tage angeben (bestehende: gbp_get_profile 'hours'). special_hours: [{date:'YYYY-MM-DD', closed:true | open_time, close_time}] — ersetzt ebenfalls alle Sonderzeiten; bestehende Perioden sind über kein Tool lesbar (gbp_get_profile liefert nur die Anzahl). validate_only: Probelauf ohne Schreiben. workspace: Slug des Kunden-Workspace (optional bei nur einem Workspace).

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

Input Schema

NameRequiredDescriptionDefault
workspaceNo
regular_hoursNo
special_hoursNo
validate_onlyNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already flag destructive and open-world behavior, but the description adds crucial specifics: both arrays replace all existing entries, all regular days must be supplied, and validate_only performs a dry run without writing. It also discloses that existing special-hour periods cannot be read through any tool.

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

Conciseness4/5

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

The purpose is front-loaded, followed by dense but relevant parameter notes. It is appropriately sized for a destructive four-parameter tool, though 'Frische-Signal' and some compact parentheticals add minor clutter.

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?

With an output schema covering returns and annotations covering safety, the description is nearly complete for invocation. The main gap is that it does not explicitly state what happens when regular_hours or special_hours are omitted or null, which matters for an optional-parameter replace-all tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must carry the burden and does: it defines all four parameters, including regular_hours fields (open_day, open_time, close_time, optional close_day), special_hours fields (date, closed, open_time/close_time), validate_only, and workspace.

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 verb and resource: set regular/special opening hours. It also distinguishes the read path by naming gbp_get_profile 'hours', so the agent can separate this write tool from the profile-read sibling.

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?

Explains the replacement rule and points to gbp_get_profile for existing regular hours, plus notes that existing special periods are not readable via any tool. It lacks an explicit when-not-to-use statement or comparison with other hour-adjacent siblings such as gbp_manage_open_info.

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