Skip to main content
Glama
driosalido

Karma MCP Server

by driosalido
OverviewSchemaRelated ServersScoreDiscussions
Python
Hybrid

get_alerts_by_state

Filter Kubernetes alerts by state (active, suppressed, or all) to monitor and analyze alert status using the Karma Alert dashboard.

Instructions

Get alerts filtered by state (active, suppressed, or all)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
stateYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • src/karma_mcp/server.py:1320-1333 (handler)
    Implementation of the 'get_alerts_by_state' tool, which filters alerts based on the 'state' parameter ('active', 'suppressed', or 'all') by calling the respective list function.
        for matcher_str in matchers.split(","):
        if "=" in matcher_str:
            key, value = matcher_str.split("=", 1)
            silence_matchers.append(
                {
                    "name": key.strip(),
                    "value": value.strip(),
                    "isRegex": False,
                    "isEqual": True,
                }
            )

# Create silence request
{

Tool Definition Quality

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states the tool 'Get alerts filtered by state' but doesn't disclose behavioral traits such as permissions needed, rate limits, pagination, or what the output contains. For a read operation with no annotation coverage, this is a significant gap.

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

Conciseness5/5

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

The description is a single, efficient sentence with zero waste. It front-loads the purpose and includes essential details without redundancy, making it appropriately sized for the tool's complexity.

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?

Given one parameter with 0% schema coverage and an output schema exists, the description is minimally adequate. It covers the purpose and parameter semantics partially, but lacks behavioral context and usage guidelines. With output schema handling return values, the description doesn't need to explain outputs, but overall completeness is limited.

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

Parameters2/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 compensate. It mentions the parameter 'state' and its values (active, suppressed, or all), adding meaning beyond the schema's generic string type. However, it doesn't explain syntax, format, or constraints, leaving the parameter partially documented.

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 verb 'Get' and resource 'alerts', with specific filtering by 'state (active, suppressed, or all)'. It distinguishes from siblings like 'list_alerts' or 'get_alert_details' by focusing on state-based filtering, though it doesn't explicitly name alternatives.

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 when filtering alerts by state, but provides no explicit guidance on when to use this tool versus siblings like 'list_active_alerts' or 'list_suppressed_alerts'. It lacks prerequisites, exclusions, or named alternatives.

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/driosalido/mcp-karma'

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