pulsenetwork

proppulse

PropPulse: Global real estate intelligence API — 10 endpoints covering the full property lifecycle. Mortgage analysis (with Rocket Mortgage/LendingTree/Better lender links), affordability, rent-vs-buy modeling,

Coverage: Global

Endpoints: • mortgage ($0.10): Mortgage analysis — jurisdiction-aware rates, payment breakdown, max price, lender links • afford ($0.10): True affordability analysis — stress-free vs. lender-qualifying ceiling, jurisdiction-aware • rentbuy ($0.10): Rent vs. buy decision model — break-even, 5-year wealth comparison, recommendation • refi ($0.08): Refinance/remortgage opportunity — break-even, monthly savings, cash-out potential • market ($0.10): Local market intelligence — buyer/seller conditions, price trends, inventory, any country • invest ($0.15): Investment property ROI — cap rate, cash-on-cash, 5-year projection, investment grade, any country • valuate ($0.10): Property valuation — AVM estimate with comparable sales and negotiation intelligence, any country • neighborhood ($0.10): Neighborhood intelligence — schools, safety, walkability, investment outlook, any country • first-buyer ($0.10): First-time homebuyer guide — jurisdiction-real schemes, loan types, step-by-step process • landlord ($0.12): Landlord toolkit — rent pricing, tenant screening, lease law, tax flags, any country • rental-market ($0.12): Rental-market intelligence — asking rent, vacancy, rent-control flag, STR + budget/hostel read, any country • council-tax ($0.05): UK Council-Tax Banding Challenge Check • council-tax-letter ($2.00): Council-Tax Challenge Document • council-tax-check ($0.25): Council-Tax Challenge Letter Preview

Input Schema

TableJSON Schema

Name	Required	Description
`zip`	No	Legacy alias for location; implies country=US when country is omitted
`beds`	No	Bed/bath description (e.g. 3/2)
`debt`	No	Existing monthly debt payments (car, student loans)
`down`	No	Down payment. Defaults to 20%.
`lang`	No	lang
`rate`	No	Current interest rate as percentage (e.g. 7.25)
`rent`	No	Current monthly rent in local currency
`sqft`	No	Square footage (improves estimate)
`type`	No	single-family / multifamily / condo / short-term
`angle`	No	renter \| investor \| str \| budget (default: overview — includes all sections)
`price`	No	Purchase price in local currency
`units`	No	Number of rental units
`years`	No	Planned years in home. Defaults to 5.
`action`	Yes	Which endpoint to call. Options: mortgage \| afford \| rentbuy \| refi \| market \| invest \| valuate \| neighborhood \| first-buyer \| landlord \| rental-market \| council-tax \| council-tax-letter \| council-tax-check
`credit`	No	Credit score range (e.g. 680)
`income`	No	Annual gross income, local currency
`address`	No	Full property address
`balance`	No	Remaining loan balance
`country`	No	Country code, e.g. US, UK, CA, DE, AU, IN (optional; unspecified is treated honestly, not silently as US)
`savings`	No	Available savings / potential down payment
`bedrooms`	No	bedrooms
`location`	No	City, region, or postal code
`priority`	No	schools / investment / walkability / safety / balanced
`situation`	No	general / finding-tenants / eviction / raising-rent / maintenance
`home_value`	No	Current home value (enables cash-out analysis)
`years_left`	No	Years remaining on current loan. Defaults to 25.
`current_band`	No	Your band (A-H, +I Wales) from gov.uk/council-tax-bands
`neighbor_bands`	No	3-5 comparable neighbors' bands, comma-separated
`purchase_price`	No	Enables deterministic gross-yield math (long-term and, when angle includes STR, short-term)
`physical_change`	No	Qualifying physical/use change (split/merge/demolition/renovation)
`band_change_date`	No	If the VOA changed the band recently
`property_address`	No	For the document
`risk_acknowledged`	No	Must be true for letters — bands can go UP (VOA verbatim warning)
`became_taxpayer_date`	No	YYYY-MM-DD — within 6 months unlocks the formal statutory proposal

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed2 schema fields changedJul 25, 2026

changedInput schema / properties / action / description

Previous value: -"Which endpoint to call. Options: mortgage | afford | rentbuy | refi | market | invest | valuate | neighborhood | first-buyer | landlord | rental-market | council-tax | council-tax-letter"New value: +"Which endpoint to call. Options: mortgage | afford | rentbuy | refi | market | invest | valuate | neighborhood | first-buyer | landlord | rental-market | council-tax | council-tax-letter | council-tax-check"

changedInput schema / properties / action / enum

Previous value: -[
-  "mortgage",
-  "afford",
-  "rentbuy",
-  "refi",
-  "market",
-  "invest",
-  "valuate",
-  "neighborhood",
-  "first-buyer",
-  "landlord",
-  "rental-market",
-  "council-tax",
-  "council-tax-letter"
-]New value: +[
+  "mortgage",
+  "afford",
+  "rentbuy",
+  "refi",
+  "market",
+  "invest",
+  "valuate",
+  "neighborhood",
+  "first-buyer",
+  "landlord",
+  "rental-market",
+  "council-tax",
+  "council-tax-letter",
+  "council-tax-check"
+]

Changed9 schema fields changedJul 8, 2026

changedInput schema / properties / action / description

Previous value: -"Which endpoint to call. Options: mortgage | afford | rentbuy | refi | market | invest | valuate | neighborhood | first-buyer | landlord | rental-market | council_tax | council_tax_letter"New value: +"Which endpoint to call. Options: mortgage | afford | rentbuy | refi | market | invest | valuate | neighborhood | first-buyer | landlord | rental-market | council-tax | council-tax-letter"

changedInput schema / properties / action / enum

Previous value: -[
-  "mortgage",
-  "afford",
-  "rentbuy",
-  "refi",
-  "market",
-  "invest",
-  "valuate",
-  "neighborhood",
-  "first-buyer",
-  "landlord",
-  "rental-market",
-  "council_tax",
-  "council_tax_letter"
-]New value: +[
+  "mortgage",
+  "afford",
+  "rentbuy",
+  "refi",
+  "market",
+  "invest",
+  "valuate",
+  "neighborhood",
+  "first-buyer",
+  "landlord",
+  "rental-market",
+  "council-tax",
+  "council-tax-letter"
+]

addedInput schema / properties / band_change_date

Added value: +{
+  "description": "If the VOA changed the band recently",
+  "type": "string"
+}

changedInput schema / properties / became_taxpayer_date / description

Previous value: -"Within 6 months unlocks the formal proposal"New value: +"YYYY-MM-DD — within 6 months unlocks the formal statutory proposal"

changedInput schema / properties / current_band / description

Previous value: -"Your band (A-H, +I Wales)"New value: +"Your band (A-H, +I Wales) from gov.uk/council-tax-bands"

changedInput schema / properties / neighbor_bands / description

Previous value: -"3-5 comparable neighbors' bands, csv"New value: +"3-5 comparable neighbors' bands, comma-separated"

addedInput schema / properties / physical_change

Added value: +{
+  "description": "Qualifying physical/use change (split/merge/demolition/renovation)",
+  "type": "string"
+}

addedInput schema / properties / property_address

Added value: +{
+  "description": "For the document",
+  "type": "string"
+}

changedInput schema / properties / risk_acknowledged / description

Previous value: -"true required for letters"New value: +"Must be true for letters — bands can go UP (VOA verbatim warning)"

Changed6 schema fields changedJul 7, 2026

changedInput schema / properties / action / description

Previous value: -"Which endpoint to call. Options: mortgage | afford | rentbuy | refi | market | invest | valuate | neighborhood | first-buyer | landlord | rental-market"New value: +"Which endpoint to call. Options: mortgage | afford | rentbuy | refi | market | invest | valuate | neighborhood | first-buyer | landlord | rental-market | council_tax | council_tax_letter"

changedInput schema / properties / action / enum

Previous value: -[
-  "mortgage",
-  "afford",
-  "rentbuy",
-  "refi",
-  "market",
-  "invest",
-  "valuate",
-  "neighborhood",
-  "first-buyer",
-  "landlord",
-  "rental-market"
-]New value: +[
+  "mortgage",
+  "afford",
+  "rentbuy",
+  "refi",
+  "market",
+  "invest",
+  "valuate",
+  "neighborhood",
+  "first-buyer",
+  "landlord",
+  "rental-market",
+  "council_tax",
+  "council_tax_letter"
+]

addedInput schema / properties / became_taxpayer_date

Added value: +{
+  "description": "Within 6 months unlocks the formal proposal",
+  "type": "string"
+}

addedInput schema / properties / current_band

Added value: +{
+  "description": "Your band (A-H, +I Wales)",
+  "type": "string"
+}

addedInput schema / properties / neighbor_bands

Added value: +{
+  "description": "3-5 comparable neighbors' bands, csv",
+  "type": "string"
+}

addedInput schema / properties / risk_acknowledged

Added value: +{
+  "description": "true required for letters",
+  "type": "string"
+}

First observedJul 6, 2026

TDQS

C2.9/5.0

Behavior2/5

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It mentions per-endpoint pricing and 'jurisdiction-aware' behavior, but fails to disclose return formats, error handling, read-only nature, or any side effects. The description emphasizes output features (e.g., 'lender links', 'recommendation') but not what the agent should expect from the response or how to handle uncertainty.

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

Conciseness2/5

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

The description is verbose and repetitive: 'any country' appears multiple times, and 'Coverage: Global' is stated twice. The glaring error of '10 endpoints' while listing 14 disrupts structure. The bullet list format helps, but the content could be consolidated significantly without losing information.

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?

With no output schema, the description must explain return values, but it only gives high-level endpoint summaries. The tool has 34 parameters, one required, and 14 action enums; the description does not explain how parameters combine with actions, nor does it clarify which parameters are mandatory for each endpoint. The complexity demands more comprehensive guidance than provided.

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%, which establishes a baseline of 3. The tool description adds context about endpoint purposes (e.g., 'afford' for stress-free vs. lender-qualifying ceiling), but it does not map which parameters are relevant to which endpoints. Some schema descriptions are tautological ('lang': 'lang', 'bedrooms': 'bedrooms'), and the tool description does not compensate for those gaps.

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 clearly identifies PropPulse as a 'Global real estate intelligence API' and enumerates specific capabilities (mortgage analysis, affordability, rent-vs-buy, etc.), which distinguishes it from sibling tools in other domains. However, it claims '10 endpoints' but lists 14 distinct actions, creating confusion about the actual scope.

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 endpoint list provides brief descriptions of what each action does, implicitly guiding selection (e.g., 'market' for local conditions, 'invest' for ROI). However, there is no explicit guidance on when to use this tool versus alternatives, nor any exclusions or prerequisites. The 'any country' caveat is useful but not framed as a decision rule.

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

All pulsenetwork tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3.2/5.0

Disambiguation4/5

Each tool has a unique domain prefix (e.g., airdroppulse, alphapulse, arbipulse) making them mostly distinguishable at a glance. A few adjacent verticals like careerpulse vs talentpulse or marketpulse vs dealpulse have overlapping themes, but their descriptions clarify the distinct focus. The utility tools (catalog_search, discover, get_openapi_spec, x402_troubleshoot) are also clearly distinct in role. However, the sheer number of similar 'pulse' names could still cause misselection without reading descriptions.

Naming Consistency4/5

The dominant naming convention is `<domain>pulse` (e.g., climatepulse, cryptopulse, edupulse), which is highly consistent and predictable. Exceptions like catalog_search, discover, get_openapi_spec, x402_troubleshoot, and stateedge break the pattern, but these are few and serve obvious utility purposes. Overall, the convention is clear and easily learnable.

Tool Count2/5

With 80 tools, the server presents an extremely large and potentially overwhelming surface. While each tool represents a distinct intelligence vertical and navigation aids exist (catalog_search, discover, get_openapi_spec), the count far exceeds the typical 3-15 range for coherent agent use and even the 'heavy' 16-25 range. The burden of selecting the correct vertical from 80 options is significant, despite clear naming.

Completeness5/5

The server offers an exceptionally broad and deep coverage of domains, from finance and health to agriculture and gaming. Each vertical includes multiple endpoints that address core operations for its domain, such as search, analysis, comparisons, deterministic checks, and even action-oriented tools like letter generators and physical mail. The presence of free discovery and troubleshooting tools fills potential gaps, leaving no obvious dead ends in the overall tool surface.

proppulse

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

TDQS

Resources