Skip to main content
Glama

Get Stream Alerts

get_alerts
Read-onlyIdempotent

[Read · free] Return recent alerts for the authenticated user's streams. An alert is emitted whenever a scheduled stream run surfaces new items. Pass unread_only=true to skip alerts the user has already marked read. Free — costs 0 credits.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMax alerts to return (default 50)
unread_onlyNoReturn only alerts that have not been marked read

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description's marginal contribution is the cost signal — "[Read · free]" and "costs 0 credits" — plus the default behavior that only unread alerts come back. It doesn't describe pagination, ordering, or what a returned alert contains, but given annotations handle safety this is a solid addition.

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?

Three short sentences, front-loaded with the read/free tag and the core action, with no filler. The only waste is mild redundancy between "[Read · free]" and the closing "Free — costs 0 credits", which say the same thing twice.

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?

This is a two-parameter, non-destructive read with full annotation coverage and no output schema, so the description doesn't owe return-value details. It supplies the concept definition, the cost, and the read-filter default — enough to call it correctly; only the ordering/format of returned alerts is left implicit.

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%, so both parameters are already documented in the schema, including the `unread_only` default and the `limit` maximum. The description restates the `unread_only=true` behavior and says nothing about `limit`, so it adds little beyond structured data — the expected baseline of 3.

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 gives a specific verb and resource ("Return recent alerts for the authenticated user's streams") and even defines what an alert is ("emitted whenever a scheduled stream run surfaces new items"), which disambiguates the concept. It does not explicitly contrast with the nearest-sounding sibling, get_stream_feed, so a reader must infer the distinction from the word "alerts".

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?

There is one concrete usage cue — pass `unread_only=true` to skip already-read alerts — but no statement of when to call this versus alternatives such as get_stream_feed, nor any exclusions. Usage is implied by the scope wording ("authenticated user's streams") rather than spelled out.

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