Skip to main content
Glama
kevynf

AKBridge MCP Server

by kevynf

sw_index_third_info

Read-onlyIdempotent

Retrieve Shenwan level-3 industry classifications from Legulegu, providing category data for stock sector analysis.

Instructions

乐咕乐股-申万三级-分类 https://legulegu.com/stockdata/sw-industry-overview#level1 :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?

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds the source URL and return type (pandas.DataFrame), but provides limited additional behavioral detail, such as data freshness or exact contents. It does not contradict the 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 short but feels like a raw docstring extraction with a Chinese title, a URL, and return tags. The URL is not directly actionable for an agent, and the structure is fragmented, though it is front-loaded with the tool's purpose.

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?

For a no-parameter read-only tool, the description is adequate for basic invocation, but it does not describe what the returned DataFrame contains (e.g., columns, codes, names). The absence of an output schema increases the need for such detail, which is missing.

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 takes zero parameters, so the input schema already covers all needed information. The description adds no parameter semantics, but none are required; the baseline of 4 applies.

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 labels the tool as '乐咕乐股-申万三级-分类' (Legulegu Shenwan Level 3 Classification) and notes it returns a pandas DataFrame. This identifies the resource and function, and the 'third' in the name distinguishes it from siblings like sw_index_first_info and sw_index_second_info, though it lacks an explicit action verb.

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 usage context is provided. The description does not state when to use this tool, what it is useful for, or when to prefer alternatives such as sw_index_first_info or sw_index_second_info. The agent receives no guidance beyond the label.

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