Skip to main content
Glama

Saved alerts

list_saved_alerts
Read-only

Canonical saved person/topic/literal phrase alerts, pause state, restore links and Following consent/cadence. Free.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered by structured data. The description still adds real behavioral context the annotations lack: the record types returned, the inclusion of pause state and restore links, and the 'Free' cost signal. It stops short of saying whether results are paginated or how many alerts come back, so a moderate score is warranted.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence fragment with zero filler, but its terseness tips into cryptic phrasing: 'restore links' and 'Following consent/cadence' are unexplained noun stacks an agent cannot confidently interpret. A short lead verb like 'List' would have made the fragment self-contained at no extra length.

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

Completeness3/5

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

For a no-param read tool with no output schema, the description is the only place an agent can learn what comes back, and it does list the returned facets. However, the meaning of several listed facets is opaque, and there is no indication of ordering, volume, or empty-state behavior, leaving the return shape only partially conveyed.

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?

The tool takes zero parameters, so there is no parameter semantics for the description to carry; the baseline for a no-param schema applies. Nothing in the description misleads about inputs, though it also never states that no arguments are accepted.

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

Purpose3/5

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

The description names the resource it covers (saved person/topic/literal-phrase alerts) but does so as a noun-phrase inventory without an explicit verb, so an agent must infer from the name list_saved_alerts that this retrieves them. The enumerated contents (pause state, restore links, Following consent/cadence) help distinguish it from siblings such as list_follows or list_people_follows, but no sibling is named as an alternative.

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

Usage Guidelines2/5

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

There is no statement of when to call this versus list_follows, list_people_follows, or find_topics, and no preconditions or exclusions. The single word 'Free' is the only usage-relevant hint, implying no credit cost, from which an agent might infer it is cheap to call liberally.

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