RentalHunter

Save a PG hunt alert

save_pg_alert

DestructiveIdempotent

Saves a PG / co-living alert for this query after the seeker agrees to share their email with partners whose listings match, and emails them when a bed matches. Requires consent true. Does not accept a phone number.

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": {
      "consent": "<consent>",
      "email": "<email>",
      "city": "<city>"
    },
    "name": "save_pg_alert"
  }
}

Input Schema

Name	Required	Description
`city`	Yes	City slug
`name`	No
`email`	Yes
`meals`	No	PG meal slots required when meals are included.
`suits`	No	PG suits: working professionals or students.
`gender`	No	PG gender filter.
`has_ac`	No	True only when AC is required. Omit or false means not required, not excluded.
`consent`	Yes	True only when the seeker has explicitly agreed, for this query, to share this email with partners whose listings match.
`sharing`	No	PG sharing types (multi-select).
`locality`	No	Exact area inside the city, such as Baner or Kharadi. A Baner search does not return Hinjewadi.
`rent_max`	No	PG max rent per bed per month (INR).
`rent_min`	No	PG min rent per bed per month (INR).
`amenities`	No	PG property amenities (all required must be present on the listing).
`hunt_name`	No
`stay_nights`	No	Desired stay length in nights (7=1 week … 330=11 months, 365=12 months). 11 months is offered everywhere; it is the standard residential lease in India.
`available_by`	No	Move-in by date, YYYY-MM-DD
`near_transit`	No	True only when near transit is required. Omit or false means not required, not excluded.
`rent_bracket`	No	PG rent brackets (multi-select, INR per bed).
`attached_bath`	No	True only when an attached bath is required. Omit or false means not required, not excluded.
`meals_included`	No	PG meals included in rent.
`near_coworking`	No	True only when near coworking is required. Omit or false means not required, not excluded.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 2, 2026

TDQS

A3.7/5.0

Behavior3/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, yet the description never explains what makes this destructive or what re-saving an identical alert does. It does add real value beyond the annotations by disclosing the outbound email side effect and the hard consent gate.

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?

Three short sentences, each load-bearing: what it creates, the email consequence, the consent precondition, and the negative constraint. No filler and the core action is front-loaded.

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?

For a 21-parameter mutation that sends email, the definition omits what a successful call returns (no output schema exists) and how idempotent re-saves behave. Coverage of the filter surface is adequate because the schema handles it, but the post-call contract 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 coverage is 86% with 21 well-annotated parameters, so the schema carries the load. The description only reinforces the consent flag and rules out a phone number — no guidance on how the many filters (rent_bracket vs rent_min/rent_max, meals vs meals_included) interact.

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 ('Saves a PG / co-living alert for this query') plus the follow-on behavior (emails when a bed matches). It narrows to PG rather than rentals, but never names its closest sibling save_hunt_alert, so an agent must infer the split.

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 a clear precondition — call only after the seeker agrees to share their email with matching partners — and an explicit exclusion ('does not accept a phone number'). It stops short of naming when to use save_hunt_alert instead.

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

All RentalHunter tools Inspect

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

Need Help?