Skip to main content
Glama

Get notified about new listings

create_search_alert
Read-onlyIdempotent

Get a link that lets the user follow a search on OLTechX: after a free signup (or sign-in) the search is saved and they receive an email and push notification for every new matching listing. Use when nothing fits now, or the user wants to wait for a better price. Does not save anything by itself.

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

Input Schema

NameRequiredDescriptionDefault
cityNo
queryNoWhat to watch for, e.g. 'RTX 4070'
categoryNo
conditionNo
max_price_eurNo
min_price_eurNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior5/5

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

Beyond the readOnly/idempotent annotations, it discloses the whole downstream flow: a free signup or sign-in gates the save, then email and push notifications fire for new matches. Crucially, 'Does not save anything by itself' reconciles the readOnlyHint with what looks like a create action, telling the agent the persistence happens in the user's signup flow rather than during the call.

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 tight sentences, front-loaded with the outcome (a link) and its consequence, followed by the use case and the non-persistence caveat. No filler, though the notification detail is slightly verbose relative to its decision value.

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?

Behavior, auth requirement, and return value (a follow link) are all covered, which is strong given no output schema. However, with six all-optional filter parameters at 17% schema coverage, an agent gets no guidance on how to construct the watched search, leaving the definition incomplete for correct invocation.

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

Parameters2/5

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

Only the 'query' parameter carries a schema description (17% coverage); city, category, condition, and both price bounds are undocumented in the schema. The description adds no meaning about these filters — nothing on how they combine, whether all are optional, or what a price range implies — so it fails to compensate for the coverage gap.

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 states a concrete action and resource — returning a link the user can follow to subscribe to a search — and distinguishes it from an immediate search via 'Use when nothing fits now.' Sibling tools are not named explicitly, so an agent must infer the contrast with search_listings, but the intent is unambiguous.

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?

It gives clear conditions for use: 'when nothing fits now, or the user wants to wait for a better price.' It also adds the caveat that the call saves nothing by itself, which prevents misuse as a persistence step. There is no explicit when-not or named alternative, which keeps it short of a 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