Skip to main content
Glama

agentlens_alerts

Create and manage alert rules for error rates, costs, or latency thresholds, and review past alert triggers.

Instructions

Manage alert rules and view alert history.

When to use: To create alerting rules for error rates, costs, or latency thresholds; manage existing rules; or review past alert triggers.

Actions:

  • list: List all alert rules

  • create: Create a new alert rule

  • update: Update an existing alert rule

  • delete: Delete an alert rule

  • history: View recent alert triggers

Example: agentlens_alerts({ action: "create", name: "High error rate", condition: "error_rate_above", threshold: 0.1, windowMinutes: 60 })

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYesAction to perform
ruleIdNoRule ID (required for update/delete)
nameNoAlert rule name (required for create)
conditionNoCondition: error_rate_above, cost_above, latency_above (required for create)
thresholdNoThreshold value (required for create)
windowMinutesNoEvaluation window in minutes (required for create)
scopeNoScope: global or agentId
notifyChannelsNoNotification channels
enabledNoEnable/disable rule
limitNoMax history results
Behavior3/5

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

No annotations provided, so description carries full burden. It lists actions and gives an example, but doesn't disclose side effects, success/failure behavior, or idempotency. Adequate but not comprehensive for a multi-action tool.

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?

Well-structured with a summary, usage section, actions list, and example. Each sentence adds value, no fluff. Front-loaded with key purpose and usage context.

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?

Given 10 parameters and no output schema, the description covers actions and provides an example. However, it lacks explicit details about return values for each action (e.g., what list returns). Still fairly complete for CRUD-like management.

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 description coverage is 100%, so the schema already documents all parameters. The description adds an example that maps params to actions, but doesn't provide significant additional meaning beyond the schema. Baseline 3 is appropriate.

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

Purpose5/5

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

The description clearly states the tool manages alert rules and views history, with specific actions (list, create, update, delete, history). It distinguishes itself from sibling tools like agentlens_analytics by focusing on alerts. The example reinforces the purpose.

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 'When to use' for creating alerting rules, managing existing rules, or reviewing triggers. Provides a concrete example. While it doesn't mention when not to use, the context is clear for typical alert management scenarios.

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/agentkitai/agentlens'

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