Skip to main content
Glama

Set an alert

set_alert
Idempotent

Set an alert on a search for the person. The first time, they sign in to Near Fine. Near Fine checks the alert for six months and emails them when a new listing turns up with everything the query asks for, such as a first edition, a signed copy or a price cap. On the Pro plan the alert keeps watching after a find and emails again when newer listings turn up; on other plans it stops after one email. The query reads as search_books reads it. Listings there already never count: the alert stays pending until its first check has noted them. Setting an alert that's already set keeps it as it is. Returns the alert, with its status and its link on Near Fine, and the person's plan: how many alerts it allows, how many are in use and how often each is checked. A full plan comes back as an error; paid plans, at plans_url, have more.

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": {
      "query": "<query>",
      "country": "<country>"
    },
    "name": "set_alert"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesISBN or title and author keywords, with anything the person wants beyond the book, as in "wolf hall signed first edition under £200"
countryYesCountry the book has to reach, as an ISO 3166-1 alpha-2 code such as US, GB or DE

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior5/5

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

Adds substantial behavior beyond annotations: six-month monitoring window, email on new listing, Pro-plan continued watching vs single email on other plans, existing listings excluded, and a full-plan error case. This is exactly the plan/auth/write semantics the annotations alone cannot convey.

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?

Purpose is front-loaded, but the definition runs long for a two-parameter tool and the phrase 'The first time, they sign in to Near Fine' is awkward and ambiguous. Several clauses about plans and returns are useful but could be tightened.

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?

Despite no output schema, the description explains the return payload (alert status, Near Fine link, plan allowance/usage/check frequency) and the error case. An agent has enough to call it and interpret the result correctly.

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 description coverage is 100%, and the schema already documents query format and the ISO country code. The description adds a useful cross-tool contract ('reads as search_books reads it') but no syntax or constraints beyond that, so baseline 3 fits.

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?

States a specific verb and resource ('Set an alert on a search') and ties the query semantics to search_books, so an agent can distinguish it from cancel_alert/list_alerts. It doesn't explicitly name those siblings as alternatives, keeping it 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 Guidelines3/5

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

Usage is implied by the alert-creating action and the idempotency note ('Setting an alert that's already set keeps it as it is'), but there is no explicit when-to-use-this-vs-cancel_alert/list_alerts guidance. An agent must infer the routing from sibling names.

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