Skip to main content
Glama

Free price alert link

alert_me
Read-onlyIdempotent

Where a person can get a free daily email when something changes: pass what to follow and get the subscribe URL to show them. kind = sku (a SKU id from search_skus: its price changes and retirement), provider (any change of a provider slug such as anthropic), category (vps, gpu, llm, inference or media), index (a series slug from get_index: moves of 5% or more) or new_model (new models of a provider). The person opens the URL, types their email address, confirms by link and gets at most one mail a day with a one-click unsubscribe. Nothing is sent from here and no address is taken by this tool. Returns an error object for an unknown target.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "kind": "<kind>",
      "target": "<target>"
    },
    "name": "alert_me"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindYesWhat kind of thing to follow
targetYesSKU id, provider slug, category, index series slug or provider slug (new_model)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds real context beyond them: no email is captured by this tool, nothing is sent, one mail per day at most, one-click unsubscribe, and an error object for unknown targets.

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 outcome before the kind enumeration, and every sentence carries information. The kind list is dense and slightly run-on, which keeps it from a 5.

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?

Although there is no output schema, the description says what is returned (a subscribe URL, or an error object for an unknown target) and covers the full user-facing lifecycle. An agent has everything needed to call it correctly.

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

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the enum is defined, yet the description still adds meaning the schema lacks: what a target actually is per kind (SKU id from search_skus, provider slug, index series slug from get_index) and the valid category values such as vps, gpu, llm, inference, media.

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?

States a concrete verb and deliverable: pass what to follow and get the subscribe URL to show the user. It clearly distinguishes the tool from actual subscription or notification sending by saying nothing is sent from 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?

Explains the human flow that motivates use (open URL, type email, confirm, at most one mail a day) and enumerates which kinds to pass. It does not explicitly exclude any case or name an alternative tool, so it falls just short of 5.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources