Skip to main content
Glama
kevynf

AKBridge MCP Server

by kevynf

macro_usa_initial_jobless

Read-onlyIdempotent

Retrieve US initial jobless claims data from 1970 to present. Use it to track weekly unemployment insurance filings and assess labor market conditions.

Instructions

美国初请失业金人数报告, 数据区间从 19700101-至今 https://datacenter.jin10.com/reportType/dc_initial_jobless :return: 美国 EIA 原油库存报告 :rtype: pandas.DataFrame

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior2/5

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

While annotations already indicate a safe read operation (readOnlyHint=true, destructiveHint=false), the description adds a date range and source URL, but it also states a wrong return type (EIA crude oil inventory). This is actively misleading about the tool's behavior and output, failing to provide accurate transparency.

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

Conciseness2/5

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

The description is short, but it includes an erroneous return line that contradicts the tool's purpose. The URL and date range are useful, but the misleading return information wastes space and harms clarity.

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 no output schema and simple annotations, the description should clarify what the returned DataFrame contains. It fails to do so and instead gives an incorrect return description. The data range and source are helpful, but the completeness is undermined by the wrong return type and lack of column/unit details.

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 there is nothing to explain beyond the schema. The baseline for 0 parameters is 4, and the description does not need to add parameter semantics.

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 initial jobless claims report (美国初请失业金人数报告) with a specific date range, distinguishing it from other macro_usa_* tools. However, the return line incorrectly mentions the EIA crude oil inventory report, which introduces confusion about the actual deliverable.

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 versus alternatives. The description does not mention any context, prerequisites, or exclusions, and with many similar macroeconomic tools available, the agent is left without direction.

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