Skip to main content
Glama

Create a deal alert

create_deal_alert

Alert the user when a brand or keyword goes on offer. Needs a MyGroceryPal account.

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": {
      "kind": "<kind>",
      "term": "<term>"
    },
    "name": "create_deal_alert"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindYesbrand: every product of a brand; keyword: product names
termYese.g. 'Cadbury' or 'oat milk'
minSavingsPercentNoPercent, 15 by default

Output Schema

NameRequiredDescriptionDefault
kindYes
termYes
minSavingsPercentYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / kind / description
      Previous value: -"'brand' follows every product of one brand; 'keyword' matches product names"New value: +"brand: every product of a brand; keyword: product names"
    • changedInput schema / properties / minSavingsPercent / description
      Previous value: -"Smallest saving worth an alert, in percent. Defaults to 15."New value: +"Percent, 15 by default"
    • changedInput schema / properties / term / description
      Previous value: -"The brand name or keyword, e.g. 'Cadbury' or 'oat milk'"New value: +"e.g. 'Cadbury' or 'oat milk'"
  2. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare this is a non-read-only mutation that is neither destructive nor open-world, so the safety profile is covered. The description adds a real behavioral fact beyond them — a MyGroceryPal account is required. It says nothing about duplicate alerts, how many alerts are allowed, or how notifications are delivered, which are the meaningful unknowns for this kind of tool.

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?

Two short sentences, front-loaded with the effect and followed by the prerequisite; nothing is wasted. The second sentence is a bare fragment, which slightly hurts polish but not clarity.

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?

The tool is simple: three parameters, full schema coverage, an output schema that covers return values, and annotations that cover the mutation profile. The description supplies the one thing structured fields cannot — the account prerequisite — so nothing essential to calling it correctly is missing.

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%, with enums and per-field descriptions for kind, term, and minSavingsPercent, so the baseline is 3. The description's mention of "brand or keyword" adds nothing beyond the kind enum already documented in the schema.

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 effect — notifying the user when a brand or keyword goes on offer — which implies creating a persistent deal alert. The verb is implicit ("Alert" rather than "Create an alert") and the link to the tool name is left for the agent to infer, but the resource and scope are clear.

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?

No when-to-use guidance and no exclusions; nothing says how this differs from searching prices or checking price history among the siblings. The only contextual statement is an account prerequisite, which is useful but not usage guidance.

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