Skip to main content
Glama
Sign In
vibeMK

vibeMK

by chexma
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

vibemk_update_timeperiod

Modify a CheckMK time period's configuration, including alias, excluded periods, exceptions, and active time ranges.

Instructions

📝 Update time period - Modify time period configuration

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "<name>"
    },
    "name": "vibemk_update_timeperiod"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesTime period name
aliasNoTime period alias
excludeNoExcluded time periods
exceptionsNoException time ranges
active_time_rangesNoActive time ranges

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.10

TDQS

B3.2/5.0
Behavior1/5

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

No annotations are provided, and the description does not disclose side effects, whether the operation is idempotent, whether it overwrites existing configuration, or whether changes require activation. This is a significant gap for a mutating operation.

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 description is concise and to the point, with no unnecessary words. It is well-structured for a simple update operation, though it could include a bit more context without becoming verbose.

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?

The description is minimal and does not mention that only provided fields are updated, that the 'name' parameter is required to identify the target, or what the tool returns. It is adequate for a simple operation but leaves some contextual gaps.

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?

The schema provides descriptions for all five parameters, so coverage is 100%. The tool description does not add deeper meaning beyond what the schema already gives; the baseline of 3 applies.

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 verb 'Update' and the resource 'time period', and explicitly says 'Modify time period configuration'. This distinguishes it from related tools like create_timeperiod, delete_timeperiod, and get_timeperiods.

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

Usage Guidelines3/5

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

The description implies usage for modifying an existing time period but does not explicitly state when to use it over alternatives (e.g., when you need to update versus create or delete). No conditions or exclusions are mentioned.

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