Skip to main content
Glama
Sign In

OwlMem

by com.owlmem
OverviewDiscussionsAdmin

kb_alerts

Read-onlyIdempotent

List the monitoring alerts sent to this space's OwlMem alert addresses (from Alertmanager, Grafana or any JSON webhook): severity, title, source, first and last seen, count, labels, description, link and the task number if one was assigned. By default only alerts that are firing, most severe first; status=all adds resolved alerts and notices (one-off messages, marked [notice]), newest first; status=notice lists only notices. Read-only.

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

Input Schema

NameRequiredDescriptionDefault
sinceNoOnly alerts that changed after this: 24h, 7d, a date such as 2026-10-25, an ISO time or unix seconds
statusNofiring (default), all, or noticefiring

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, and the description's trailing 'Read-only' merely repeats that. The genuinely additive context is ordering behavior (severity order by default, newest-first for status=all) and the '[notice]' marking convention. No mention of pagination, limits, or empty-result behavior.

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?

Front-loaded with the resource and its source systems, then mode semantics in a single dense but readable sentence. The closing 'Read-only' sentence is redundant with the annotations and does not earn its place.

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

Completeness4/5

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

With no output schema, the description does the work of listing return fields, defaults, and ordering, which is enough to call the tool correctly with either parameter omitted. The remaining gap is the unclear boundary with the sibling kb_notices, which matters for tool selection.

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

Parameters4/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 earns an extra point by explaining what each status value actually includes and how ordering changes between them, which the terse enum descriptions do not convey. The 'since' parameter is left entirely to the schema.

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?

Specific verb+resource: lists monitoring alerts received via this space's alert addresses, and enumerates the fields returned (severity, source, first/last seen, count, labels, link, task number). It's clear what the tool is. However, it doesn't distinguish itself from the sibling kb_notices, which arguably overlaps with the 'notice' concept surfaced here.

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

Usage Guidelines4/5

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

Explicitly states the default mode (firing only, most severe first) and what each status value selects (all adds resolved + notices, newest first; notice lists only notices). That is real mode-selection guidance. What's missing is any routing advice toward siblings such as kb_notices or kb_inbox.

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

All OwlMem toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources