Skip to main content
Glama

AlertForge

by io.github.lasan713
OverviewDiscussionsAdmin

Plan an AI Alert pack

plan_alert_pack

Requires an approved AlertForge account connection. OAuth-aware clients should start AlertForge's secure authorization flow and ask the user only to sign in and approve. Setup: https://alertforge.ai/ai-agents#agent-setup. Free to call -- prices a proposed AI Alert pack WITHOUT spending any credits or creating anything. Supports a single alert, a handful, or the full set of 7: pass alerts with only the keys you want (e.g. one entry to create just one alert), or omit alerts entirely for the full 7-alert pack. Requires characterImageUrl -- your own uploaded/generated character (see generate_alert_character). Returns a planId (valid 24 hours, single-use) plus the exact credit cost -- show that to the user and get confirmation before calling create_alert_pack with this planId.

Input Schema

NameRequiredDescriptionDefault
themeNoOverall visual theme/direction for every alert, up to 400 characters.
alertsNoWhich alerts to include. Omit this field entirely for the full 7-alert pack. If provided, ONLY the keys listed here are created -- e.g. a single {key:"follow"} entry creates exactly one alert. Call list_alert_types first for the valid keys.
packNameNoDefaults to 'AI Alert Pack'.
captionColorNo#RRGGBB fill for every alert's on-screen caption text (applies to the whole pack, not per-alert). Falls back automatically if too close to the character's chroma-key colour.
paletteHexesNoUp to 8 #RRGGBB colours to steer the pack's look.
generateAudioNoWhole-pack audio toggle. Defaults true.
characterImageUrlYesYour own character image: the path/url returned by generate_alert_character (once complete) or your own upload, or a safe https:// URL. Required.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior1/5

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

Annotations mark the tool readOnlyHint=false, but the description says it operates "WITHOUT ... creating anything" even though it returns a single-use planId, which is a persisted artifact. That is a direct inconsistency with the non-read-only annotation; the auth, no-credit, and 24h expiry details are otherwise useful.

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?

It is front-loaded with auth and cost, then usage and return behavior. However, the alerts subset explanation repeats schema text and makes the description longer than necessary.

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

Completeness5/5

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

For a complex, auth-gated planning tool with no output schema, the description covers credentials, setup, cost, planId lifetime/single-use, required character image, and next step. This is complete enough for 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%, and the schema already documents alerts omission/subset behavior, characterImageUrl, defaults, and enum tiers. The description reinforces the alerts semantics but adds no new parameter format or constraints beyond the schema, so 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 states the tool prices/proposes an AI Alert pack and distinguishes it from create_alert_pack by requiring a planId and confirmation step. It also specifies single vs full-pack behavior, so an agent can identify the tool's role among siblings.

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

Usage Guidelines5/5

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

It gives an explicit call sequence: get a character via generate_alert_character, use list_alert_types for keys, show planId/cost to the user, and confirm before calling create_alert_pack. It also says to omit alerts for the full pack or provide only the desired subset.

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

All AlertForge 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