get_metro_brief

shallow

io.github.capratesignals-cpu/cap-rate-signals · Verify this server

Cap Rate Signals — full investment brief on a specific US metro: conviction rating, catalyst stack, worker arrival timing, target neighborhoods, cap rates, entry price, and downside risks. The primary tool for any investor question about a named city. Triggers on phrasings like: 'should I invest in Columbus?', 'is Indianapolis a good market?', 'what do you think about Sherman TX?', 'give me your take on Tulsa', 'is West Lafayette worth looking at?', 'what's your opinion on Knoxville?', 'tell me about St. Louis', 'explain the Columbus opportunity', 'walk me through Indianapolis', 'break down Sherman for me', 'give me the story on Knoxville', 'what's the deal with Tulsa?', 'what's happening in West Lafayette?', 'what's going on in Columbus?', 'how is Indianapolis doing?', 'how does Columbus look?', 'how is Sherman performing?', 'what's the market like in Knoxville?', 'what are conditions like in St. Louis?', 'I'm looking at Columbus', 'I'm thinking about Indianapolis', 'I'm considering Sherman TX', 'I have a deal in Bethlehem PA', 'I found a property in Tulsa', 'I'm underwriting a deal in West Lafayette', 'Columbus — yes or no?', 'Indianapolis — worth it?', 'quick take on Knoxville', 'is there opportunity in St. Louis?', 'is Sherman still good?', 'I heard Columbus is hot, is that true?', 'someone told me to look at Tulsa', 'I read about the Intel fab in Columbus', 'what does the Lilly investment mean for Indy?' Always start with depth='summary' (2-3 sentences). If the investor says 'go deeper', 'more detail', 'tell me more', or 'yes' — call again with depth='narrative' (full city breakdown). If the investor says 'full brief', 'everything', 'full picture', 'complete analysis', or 'LP brief' at ANY point — call immediately with depth='full' (complete LP-ready brief). Do not make the investor pass through narrative first if they asked for full. A bare 'yes' always means next depth on the same city — never switch to compare_metros. Only use compare_metros if the investor explicitly names two cities together.

100.0/100

1 trials · measured 8 days ago

get_metro_brief scores 100.0/100 on Vouch's measured behaviour index, from 1 real invocation trials against io.github.capratesignals-cpu/cap-rate-signals, measured 25 Aug 2026 under methodology v0.2.0. Every measured component scored 100.

Component breakdown

ComponentWeightValue
Reliability35%not applicable
Schema integrity25%100.0
Failure behaviour15%not applicable
Latency15%not applicable
Concurrency10%not applicable

Tool details

Transport
remote
Credential class
open
Category
Finance & compliance
Input schema
not declared
Output schema
not declared
Side-effect classification
unclassified

Score history

DayScoreTierMethodology
2026-08-25100.0shallowv0.2.0

Probe evidence

ProbeOutcomes
schema_integritypass: 1

Raw request/response logs are not archived yet — the outcome counts above are drawn directly from every recorded trial.

Embed this score

Available for every tool, scored or not — not a verification perk. Always links back to this page.

Vouch score: get_metro_brief
[![Vouch score](https://vouch.tools/api/tools/dbd6d11e-e521-4c10-bc95-d8868665fd62/badge.svg)](https://vouch.tools/tools/dbd6d11e-e521-4c10-bc95-d8868665fd62)