Skip to main content
Glama
Sign In

NeedToFind

by app.needtofind
OverviewDiscussionsAdmin

Set Alert Tool

set_alert

Create an alert so the user is emailed when someone posts a wanted ad matching their keywords and/or category (for sellers who want to hear about demand for what they have). Every keyword must appear in the ad's title or description. Needs at least keywords or a category. Up to 10 alerts per user. Only affects ads posted after the alert is created.

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

Input Schema

NameRequiredDescriptionDefault
categoryNoOnly ads in this category
keywordsNoWords that must all appear in the ad, e.g. "yanmar injector"

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / category / enum
      Previous value: -[
-  "Electronics",
-  "Furniture",
-  "Clothing & Accessories",
-  "Vehicles",
-  "Musical Instruments",
-  "Sports & Outdoors",
-  "Tools & Hardware",
-  "Boats & Marine",
-  "Collectibles & Antiques",
-  "Books & Media",
-  "Toys & Games",
-  "Other"
-]New value: +[
+  "Antiques",
+  "Appliances",
+  "Arts & Crafts",
+  "Baby & Kid",
+  "Barter",
+  "Beauty & Health",
+  "Bike Parts",
+  "Bikes",
+  "Books",
+  "Business",
+  "CDs / DVD / VHS",
+  "Cell Phones",
+  "Clothes & Accessories",
+  "Collectibles",
+  "Computer Parts",
+  "Computers",
+  "Electronics",
+  "Farm & Garden",
+  "Free",
+  "Furniture",
+  "General",
+  "Household",
+  "Jewelry",
+  "Materials",
+  "Music Instruments",
+  "Photo & Video",
+  "Sporting",
+  "Tickets",
+  "Tools",
+  "Toys & Games",
+  "Video Gaming",
+  "ATV / UTV / Snow",
+  "Auto Parts",
+  "Aviation",
+  "Boat Parts",
+  "Boats",
+  "Cars & Trucks",
+  "Heavy Equipment",
+  "Motorcycle Parts",
+  "Motorcycles",
+  "RVs & Camping",
+  "Trailers",
+  "Wheels & Tires"
+]
  2. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations only declare openWorldHint=false and destructiveHint=false, so the description carries the real behavioral load and does so well: it discloses the matching rule (every keyword must appear in title or description), the quota, and the non-retroactive scope ('Only affects ads posted after the alert is created'). These are exactly the traits an agent cannot infer from structured fields.

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?

Five tight sentences, front-loaded with the action and outcome, then constraints. The parenthetical use-case clause grounds the tool's audience without padding.

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?

For a two-parameter creation tool with no output schema, the description covers purpose, matching logic, prerequisites, quota, and temporal scope. An agent has everything needed to decide and invoke correctly.

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?

Schema coverage is 100%, so baseline is 3, but the description adds matching semantics beyond the schema: keywords are AND-combined and must appear in the ad title or description, and category acts as a filter. The enum list itself is left to the schema, which is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Create an alert') and explains the triggering semantics: an email when a wanted ad matches keywords and/or category. This clearly distinguishes it from siblings like delete_alert, list_alerts, and search_wants.

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?

Gives the use context ('sellers who want to hear about demand'), the prerequisite ('Needs at least keywords or a category'), and the cap ('Up to 10 alerts per user'). It does not name an alternative tool for one-off searching, but the when-to-use condition is unambiguous.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All NeedToFind toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources