Skip to main content
Glama

List alerts

list_alerts
Read-onlyIdempotent

List the person's alerts on Near Fine. The first time, they sign in. Finds come first, then alerts being checked, then the rest, newest first. Each has its id, query, country, status, when it was set, last checked and runs until, a link to it on Near Fine, how many times it has emailed a find and when it last did, and, once it has found a listing, the cheapest it last found: its title, seller, condition, price and shipping in the person's currency, and the URL to buy it. Statuses: pending (noting what's listed already), live (watching, as a Pro alert stays after a find), found (emailed a find and stopped), ended (the person got the book or stopped it), expired (ran its six months) and paused (the plan has room for fewer alerts). Also returns the person's plan.

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_alerts"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior5/5

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

Annotations already establish readOnly, idempotent, non-destructive, closed-world behavior, and the description adds substantial context beyond that: sign-in on first use, result ordering (finds first, then checked alerts, then rest newest-first), and detailed status semantics. This is exactly the kind of behavioral disclosure that helps an agent interpret the response correctly.

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 opening sentence is front-loaded and useful, but the description then becomes a long run-on inventory of return fields and statuses. The information is relevant because there is no output schema, but the structure is loose and several clauses are hard to scan.

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?

With no output schema, the description does the heavy lifting by explaining what each alert contains, how alerts are ordered, what each status means, and that the person's plan is also returned. It is nearly complete for a no-parameter listing tool, though it does not address pagination or edge cases such as an empty alert list.

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 has zero parameters, so the baseline is 4. There are no parameter semantics to explain, and the description appropriately uses its space on return data and status behavior instead.

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 starts with a specific verb and resource: "List the person's alerts on Near Fine." That is clear enough for an agent to understand the operation without opening the schema. It does not explicitly differentiate itself from siblings such as set_alert or cancel_alert, so it stops short of a 5.

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 explicit when-to-use guidance or comparison to alternatives like set_alert, cancel_alert, search_books, or list_sources. The description implies listing is for viewing alerts, but it never states when this tool should be chosen over another tool.

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