Skip to main content
Glama
kevynf

AKBridge MCP Server

by kevynf

macro_usa_cb_consumer_confidence

Read-onlyIdempotent

Access historical US Conference Board Consumer Confidence Index data from 1970 to today for economic analysis and decision-making.

Instructions

金十数据中心-经济指标-美国-领先指标-美国谘商会消费者信心指数报告, 数据区间从 19700101-至今 https://datacenter.jin10.com/reportType/dc_usa_cb_consumer_confidence :return: 美国谘商会消费者信心指数报告 :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?

Beyond annotations (readOnlyHint=true, idempotentHint=true), the description adds useful context: the data range from 19700101 to present, the source URL, and the return type as a pandas DataFrame. However, it does not disclose any pagination, column specifics, or rate limit behavior, which would enrich transparency.

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

Conciseness4/5

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

The description is relatively concise, but it repeats '美国谘商会消费者信心指数报告' almost verbatim in the title and the return field, creating minor redundancy. It is front-loaded with the core purpose and includes a URL and return type without excessive filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's simplicity (zero parameters, no output schema), the description covers the essential aspects: data source, time range, and return format. It is complete enough for an AI agent to select and invoke the tool correctly, though it does not list specific DataFrame columns or any error conditions.

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 tool has zero parameters, so the schema covers everything. The description adds no parameter-specific details, which is acceptable and matches the baseline for parameterless tools.

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 the tool as providing the US Conference Board Consumer Confidence Index report from Jin10 Data Center, with a specific data range. Though it lacks an explicit verb like 'get' or 'retrieve', the resource is unambiguous and distinct from sibling tools such as macro_usa_michigan_consumer_sentiment.

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 description implies its use for retrieving the specified indicator, but does not explicitly state when to prefer this tool over alternatives, nor does it mention exclusions or when not to use it. The specificity of the resource provides some contextual guidance, but no direct comparison to sibling tools.

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