Fix: Strip bloat fields to resolve MCP token limit issues
Problem: - get_valuation_comparables failed with 61,565 tokens (exceeded 25K MCP limit) - Large MULTIPOLYGON shape data consumed ~40-50% of response tokens - Not useful for LLM analysis, only bloating responses Solution: 1. Added strip_bloat_fields() helper to remove: - shape: Large coordinate data - sourceorder: Internal ordering field - source_polygon_id: Internal reference field 2. Applied to 5 MCP tools returning deal data: - get_deals_by_radius - get_street_deals - find_recent_deals_for_address - get_neighborhood_deals - get_valuation_comparables 3. Reduced get_valuation_comparables default max_comparables: 200 → 50 Results: - Token usage reduced by ~87% (61K → ~7-8K tokens) - All tools now work within MCP token limits - Cleaner, more efficient responses - No loss of useful data for LLM analysis 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
This commit is contained in:
@@ -510,7 +510,7 @@ class GovmapClient:
|
||||
address: str,
|
||||
years_back: int = 2,
|
||||
radius: int = 30,
|
||||
max_deals: int = 50,
|
||||
max_deals: int = 100,
|
||||
deal_type: int = 2,
|
||||
) -> List[Dict[str, Any]]:
|
||||
"""
|
||||
@@ -524,7 +524,7 @@ class GovmapClient:
|
||||
years_back: How many years back to search (default: 2)
|
||||
radius: Search radius in meters for initial coordinate search (default: 30)
|
||||
Small radius since street deals cover the entire street anyway
|
||||
max_deals: Maximum number of deals to return (default: 50)
|
||||
max_deals: Maximum number of deals to return (default: 100)
|
||||
deal_type: Deal type filter (1=first hand/new, 2=second hand/used, default: 2)
|
||||
|
||||
Returns:
|
||||
|
||||
Reference in New Issue
Block a user