get_housing
Get latest housing starts and existing home sales data from FRED
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Slacking.biz — SEC Financial Data + US Economics + Demographics + FX
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
A3.6/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description is minimal and does not disclose behavioral traits such as data update frequency, range, or any limitations. However, it correctly implies a read-only operation, and there is no annotation to contradict. It provides basic context but could elaborate on what 'latest' means.
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?
The description is a single sentence that conveys all essential information without unnecessary words. It is front-loaded and efficient.
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?
Given the lack of output schema and annotations, the description should provide more context about what the tool returns, such as data format, date range, or units. Without it, the agent lacks sufficient information to use the tool correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters4/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
With zero parameters and 100% schema description coverage, the description does not need to explain parameters. The baseline for 0 parameters is 4, and the description meets that by not requiring additional param details.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly specifies the action ('Get'), the resource ('latest housing starts and existing home sales data'), and the source ('FRED'). This clearly differentiates it from sibling tools like get_gdp or get_inflation, which cover different economic indicators.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines2/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is provided on when to use this tool versus alternatives. Sibling tools like get_econ_summary might also include housing data, but the description offers no context for selection or 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.
TDQS
C2.9/5.0
Disambiguation2/5
Several tool groups have overlapping purposes: fda_drug_labels vs health_drug_search, fda_recalls vs health_recalls, fx_official_rates vs treasury_fx_rates, treasury_debt vs us_debt_current, and get_gdp vs get_bea_gdp. These near-duplicates create real ambiguity for an agent deciding which tool to call.
Naming Consistency2/5
Names mix verb-led styles (get_, search_, compare_, screen_) with domain-led styles (fx_, treasury_, uk_, health_, eurostat_, datausa_). Within the same domain, similar actions use different patterns (get_gdp vs eurostat_gdp vs imf_indicator), making the set feel inconsistent and hard to predict.
Tool Count1/5
75 tools is extreme for any MCP server, especially when many tools are redundant or cover unrelated domains (weather, earthquakes, scholarly search, air quality) outside the stated SEC/economics/demographics/FX focus. This overwhelms agents and burdens context windows.
Completeness3/5
Core domains like SEC financials, major economic indicators, basic demographics, and current FX rates are well covered. However, gaps remain: no historical FX rates, no stock price/quote tool, limited demographic breakdowns, and no ability to fetch full SEC filing text. Some operations end in dead ends.