Skip to main content
Glama
kevynf

AKBridge MCP Server

by kevynf

macro_usa_nahb_house_market_index

Read-onlyIdempotent

Retrieves the US NAHB Housing Market Index report from 1985 to present, returning historical data as a pandas DataFrame for housing market analysis.

Instructions

美国NAHB房产市场指数报告, 数据区间从 19850201-至今 https://datacenter.jin10.com/reportType/dc_usa_nahb_house_market_index :return: 美国NAHB房产市场指数报告 :rtype: pandas.DataFrame

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior3/5

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

Annotations already indicate readOnlyHint=true, destructiveHint=false, and idempotentHint=true, covering the safety profile. The description adds the data range and specifies the return type as pandas.DataFrame, providing some behavioral context. However, it does not describe data frequency or content details, so it is adequate but not rich.

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

Conciseness3/5

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

The description is brief but repeats the report name three times and includes a URL that may not be necessary for an agent. It could be more streamlined, though it is still relatively short.

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?

The tool has no parameters and no output schema, so the description's mention of return type and date range helps. However, it lacks explanation of what the NAHB index measures or how the returned data is structured, which is a gap for an agent encountering this tool among many similar macro indicators.

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?

The input schema has zero parameters, so the description does not need to explain parameters. The baseline of 4 applies because there are no parameters to document.

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 states this is the US NAHB housing market index report with a specific date range (from 19850201 to present), giving a clear resource and scope. However, it does not explicitly differentiate from sibling tools like macro_usa_house_price_index or macro_usa_exist_home_sales, so it lacks sibling differentiation.

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?

There is no guidance on when to use this tool compared to alternatives. It only describes what the tool provides, without any context on use cases or exclusions, earning a low score for usage guidance.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/kevynf/akbridge'

If you have feedback or need assistance with the MCP directory API, please join our Discord server