Skip to main content
Glama

Airsockfly

Create price alert

create_price_alert

Create a price alert for an offer. The user is notified when the price drops to the threshold.

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": {
      "vertical": "<vertical>",
      "externalId": "<externalId>",
      "title": "<title>",
      "thresholdGrosze": "<thresholdGrosze>"
    },
    "name": "create_price_alert"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleYesAlert name shown to the user.
subtitleNoOptional second line shown with the alert.
verticalYesService type.
externalIdYesOffer identifier (externalId) returned by a search tool.
thresholdGroszeYesNotify when the price drops to this amount or lower, in grosze (1/100 PLN).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

The description adds useful behavioral context beyond the annotations: the alert notifies the user when the price reaches the threshold. The annotations already establish that this is a non-read-only, non-destructive, non-idempotent write. The description does not warn that repeated calls may create duplicate alerts or explain the notification channel, leaving some behavioral gaps.

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

Conciseness5/5

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

The description is two short sentences with the action front-loaded and zero wasted wording. The second sentence adds useful outcome context without expanding into unnecessary detail.

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?

For a five-parameter create tool with a fully documented schema and informative annotations, the description covers the core action and user-visible outcome. It lacks a duplicate-creation caution and does not describe what the created alert response contains, but those gaps are modest given the structured metadata.

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%, so all five parameters are already documented in the schema. The description only restates the offer and threshold concepts without adding syntax, sourcing, or edge-case meaning. That meets the baseline when the schema carries parameter semantics.

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 specific verb and resource: "Create a price alert for an offer." It also explains the alert's trigger condition. It does not differentiate from sibling tools such as list_price_alerts or delete_price_alert, so it falls 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?

The description implies usage by saying the alert applies to an offer and fires when the price drops to the threshold. It does not explicitly state when to use this tool rather than alternatives, nor does it give exclusions or prerequisites. The intended use is inferable, but only minimally guided.

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