Skip to main content
Glama
kevynf

AKBridge MCP Server

by kevynf

business_value_artist

Read-onlyIdempotent

Fetch artist commercial value data from Endata. Returns a pandas DataFrame with business value metrics for entertainment analytics.

Instructions

艺恩-艺人-艺人商业价值 https://www.endata.com.cn/Marketing/Artist/business.html :return: 艺人商业价值 :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?

The description discloses the return type (pandas.DataFrame) and a source URL, but it does not describe any behavioral traits beyond the read-only, idempotent, and non-destructive annotations already provided. It fails to mention what columns, time periods, or data scope the returned DataFrame contains. There is no contradiction with annotations.

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 and includes a useful URL and return type, but the first line '艺恩-艺人-艺人商业价值' is redundant as it essentially duplicates the tool name. The structure has some wasted text, lowering the score.

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?

For a no-parameter tool, the description still leaves the output vague – '艺人商业价值' does not specify what data is actually included. With no output schema, the description would need to explain the returned DataFrame's structure to be complete, but it does not. The annotations cover safety but not the data content.

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 (empty input schema), so the baseline is 4. The description does not need to explain parameters, and nothing is missing regarding parameter semantics. The mention of the return type is not directly relevant to parameters.

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

Purpose2/5

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

The description primarily restates the tool name as '艺恩-艺人-艺人商业价值' and repeats it in ':return: 艺人商业价值'. It lacks a verb or clear operation statement such as 'retrieves' or 'queries'. The URL provides a source but does not clarify what the tool does. This is essentially a tautology of 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 given on when to use this tool or how it compares to alternatives. It does not mention any use cases, prerequisites, or distinctions from similar tools like online_value_artist. The rubric marks 'no guidance' as a 2.

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