Skip to main content
Glama
k9fr4n

thruk-mcp

by k9fr4n

thruk_perfdata_snapshot

Fetch parsed performance data for services matching a customizable filter based on host, group, state, or custom variables.

Instructions

Parsed performance data for every service matching filter (one call).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of services to scan (max 1000).
filterNoStructured filter tree supporting AND/OR nesting. Two node types: leaf: {"type":"leaf", "field":"...", "op":"...", "value":...} group: {"type":"group", "operator":"and"|"or", "conditions":[...]} Available fields: custom_var, description, host, host_custom_var, hostgroup, servicegroup, state Operators: eq, gte, in, lte, neq, regex Examples: # Hosts DOWN in HG_AGILE: {"type":"group","operator":"and","conditions":[ {"type":"leaf","field":"hostgroup","op":"eq","value":"HG_AGILE"}, {"type":"leaf","field":"state","op":"eq","value":"down"} ]} # Hosts in HG_AGILE OR with KERNEL=windows: {"type":"group","operator":"or","conditions":[ {"type":"leaf","field":"hostgroup","op":"eq","value":"HG_AGILE"}, {"type":"leaf","field":"custom_var","op":"eq","value":{"var":"KERNEL","val":"windows"}} ]}
backendsNoComma-separated backend names (sites). Omit for all backends.
Behavior2/5

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

With no annotations, the description should disclose behavioral traits. It only mentions 'one call' and 'parsed performance data,' omitting details on side effects, read-only status, pagination, or rate limits.

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 extremely concise, using a single sentence. While efficient, it lacks structured presentation, but no words are wasted.

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?

Despite detailed parameter schema, the description fails to explain what 'parsed performance data' entails, return format, or any limitations (e.g., max 1000 limit). This is insufficient for a tool with no output schema.

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 input schema has 100% description coverage, so parameters are already well-documented. The tool description adds no extra semantic meaning beyond what the schema provides.

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 it returns 'parsed performance data' for services matching a filter, and notes it's a single call. However, it does not differentiate from similar sibling tools like thruk_get_perfdata.

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?

No guidance is provided on when to use this tool versus alternatives. The phrase 'one call' hints at efficiency but lacks explicit when-to-use or when-not-to-use context.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/k9fr4n/thruk-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server