Skip to main content
Glama
kevynf

AKBridge MCP Server

by kevynf

macro_canada_gdp_monthly

Read-onlyIdempotent

Fetches Canada's monthly GDP growth rate (month-over-month) from Eastmoney, providing economic indicator data for analysis.

Instructions

东方财富-经济数据-加拿大-GDP 月率 https://data.eastmoney.com/cjsj/foreign_7_9.html :return: GDP 月率 :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?

Annotations already declare readOnly, idempotent, and non-destructive hints. The description adds a pandas.DataFrame return type and a source URL but no additional behavioral context such as date range, units, frequency, or potential quirks. There is no contradiction with annotations, but the added value is minimal.

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 extremely short, front-loaded with the title, then source URL and return type. It is concise with minimal repetition, though the URL may be of limited value for an AI agent deciding to invoke the tool.

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?

With no output schema, the description should explain what the returned DataFrame contains. It only states 'GDP月率' (GDP monthly rate), which is vague and lacks details on columns, units, historical depth, or the exact metric (e.g., month-over-month growth rate). An agent would have to inspect the data to understand its structure.

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 is fully complete. Per the rubric, a 0-parameter tool receives a baseline of 4; the description does not need to add parameter details since none exist.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly identifies the resource (Canada GDP monthly rate) via the Chinese title and return line, but it lacks an explicit verb and is essentially a restatement of the tool name. It does not differentiate from closely related sibling tools like macro_canada_cpi_monthly or macro_canada_bank_rate beyond the name.

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. The description only includes a source URL and return type, with no mention of preferred use cases, exclusions, or comparison to other macro indicators.

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