Skip to main content
Glama
Sign In
vibeMK

vibeMK

by chexma
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

vibemk_list_rulesets

List all available rulesets in CheckMK, showing basic information. Supports limiting the number returned and including deprecated rulesets.

Instructions

📋 List all rulesets - Show all available rulesets with basic information

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

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of rulesets to return
show_deprecatedNoInclude deprecated rulesets in the list

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.10

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, and the description does not explicitly state that this is a read-only operation or mention any side effects. It is implied by 'list', but not disclosed.

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 very concise, but it contains slight redundancy ('List all' and 'Show all available'). It is well-structured and free of fluff.

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?

For a simple list operation, the description is adequate. It does not specify the exact content of 'basic information' or clarify the difference from get_rulesets, but it is not misleading. Given the existence of many similar tools, a bit more context would be helpful.

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 descriptions for both parameters (limit and show_deprecated) are clear and cover 100% of the parameters. The description itself adds no additional parameter information, so baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool lists all rulesets with basic information, using a specific verb and resource. It is distinguishable from similar tools like search_rulesets or get_ruleset, though it doesn't explicitly differentiate them.

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?

The description provides no guidance on when to use this tool versus alternatives like search_rulesets or get_rulesets. It only states the action without conditions or recommendations.

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