Skip to main content
Glama
Sign In
thruk-mcp

thruk-mcp

by k9fr4n
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

thruk_checks

Enable or disable active checks for a host or service to control monitoring behavior.

Instructions

Enable or disable active checks for a host or service.

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": {
      "host": "<host>",
      "enabled": "<enabled>"
    },
    "name": "thruk_checks"
  }
}

Input Schema

NameRequiredDescriptionDefault
hostYesHost name
cascadeNoWhen true and no service is specified, also apply to all services of the host. Ignored when service is set.
enabledYesTrue to enable active checks, False to disable.
serviceNoService description. Omit to target the host only (use cascade=true to also cover all its services).
backendsNoComma-separated backend names (sites). Omit for all backends.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations provided, the description bears full responsibility for disclosing behavioral traits. It states the action (enable/disable) but fails to mention side effects (e.g., immediate impact on monitoring, dependency on backend availability, or whether changes are persistent). Agents need more detail to assess risk.

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 a single sentence that efficiently states the core function, with no redundant words. However, it could be improved by front-loading key constraints (e.g., 'for a specific host or service') without adding bulk. It is concise but slightly under-informative for the number of parameters.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool modifies state, has 5 parameters, no output schema, and no annotations, the description is insufficient. It omits return values, error conditions, and practical examples. For a mutation tool with conditional logic (cascade, backends), the description should provide more complete context to guide correct invocation.

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?

Schema coverage is 100%, so baseline is 3. The description adds no parameter-specific detail beyond the schema, just an overall statement. It doesn't explain how 'cascade' works or the role of 'backends' beyond what's in the schema, so no extra value is provided.

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 verb 'Enable or disable' is specific and the resource 'active checks for a host or service' is clear. However, it does not differentiate from sibling tools like thruk_recheck or thruk_stale_checks, which also modify check behavior. Without distinction, the agent may not understand when to choose this over others.

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, no prerequisites, and no exclusions. For example, it doesn't mention that disabling checks is distinct from scheduling downtime or acknowledging problems. The agent is left to infer usage context on its own.

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