Skip to main content
Glama

SalonRenter for Muse

save_search_alert

Save a search alert on the signed-in renter account. city or state is required.

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

Input Schema

NameRequiredDescriptionDefault
cityNo
emailNo
stateNo
listingTypeNo
maxWeeklyPriceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full burden. It discloses that the alert is tied to the signed-in account (implying auth is handled externally) and that a geo filter is mandatory, but says nothing about duplicate-alert behavior, whether email drives delivery, whether the save is reversible, or what the response returns. For a write tool with zero structured behavioral hints this is thin.

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 action and followed by the key constraint; nothing is padded. The second sentence is elliptical ("city or state is required" for what?) but the economy is appropriate.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

A 5-parameter mutation tool with no annotations, no output schema, and no parameter documentation needs substantially more description than two sentences. The agent lacks the value semantics for three of five fields and any notion of side effects or idempotency.

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?

Schema description coverage is 0% across 5 parameters, and the description only clarifies city/state. email, listingType, and maxWeeklyPrice are left entirely undefined, so an agent cannot tell whether email is the notification address, what values listingType accepts (no enums), or what unit maxWeeklyPrice uses. Note the description's "city or state is required" also conflicts with the schema declaring zero required properties.

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 ("Save a search alert") plus the scope ("on the signed-in renter account"), which is enough to distinguish it from the read-oriented siblings like search_listings and get_listing. It stops short of naming any sibling explicitly, so it lands at 4 rather than 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 clause "city or state is required" functions as a usable invocation prerequisite, which is more than nothing. However, there is no guidance on when an agent should create an alert versus simply running search_listings, no mention of what happens if the renter already has an equivalent alert, and no exclusions.

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