Skip to main content
Glama
Sign In
awesome-student-ai-skills

awesome-student-ai-skills

by cuic19053-hue
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

list_student_skills

Lists all 35 supported university student proposal/application tracks, optionally filtered by category such as research, competition, scholarship, honor, practice, or military service.

Instructions

列出所有支持的高校学生申报书与申请材料赛道（共 35 个）。

参数:
  category: 可选分类过滤。支持:
    - 'research': 科研立项 / 大创（创新训练、创业训练、创业实践等）
    - 'competition': 学科竞赛（挑战杯、互联网+、红旅赛道等）
    - 'scholarship': 奖学金（国家奖学金、国家励志、校级、企业专项等）
    - 'honor': 荣誉评优（优秀毕业生、三好学生、优秀学生干部等）
    - 'political': 政治身份（入团申请、思想汇报、转正申请等）
    - 'practice': 实践活动（三下乡社会调查、支教、科技服务、西部计划等）
    - 'study_abroad': 公派留学 / 国际交流
    - 'military': 应征入伍
    - 'other': 转专业等

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_student_skills"
  }
}

Input Schema

NameRequiredDescriptionDefault
categoryNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. The word '列出' (list) makes the read-only nature obvious and the risk is minimal, and the total count (35) hints at the result size; however, it says nothing about ordering, pagination, or whether an invalid category errors or returns empty.

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 first line front-loads purpose and scope; the parameter block is structured as a bulleted value list that is easy to scan. Slightly long for one parameter, but every enumerated value carries real disambiguation value.

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?

An output schema exists, so return-value shape need not be described. For a single-optional-parameter enumeration tool, the description covers everything needed to call it correctly; only edge-case behavior (unknown category, empty results) is left unspecified.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% — the input schema defines `category` only as a bare nullable string with no enum or description. The description fully compensates by enumerating all nine valid values with concrete Chinese examples for each (e.g., 'challenge cup / internet+ / red-tour tracks' for competition), which is exactly what the schema omits.

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?

States a specific verb+resource: '列出所有支持的高校学生申报书与申请材料赛道（共 35 个）' — an enumeration of supported student application/declaration tracks, with the count given. It is clearly distinguishable from detail-oriented siblings like get_skill_info or get_skill_requirements, though it never names them explicitly.

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 verb 'list' implies usage as a discovery/entry point, and the optional filter suggests it can be used to narrow before routing. But there is no explicit 'use this when…' guidance, no mention of when to prefer route_student_skill or get_skill_info instead, and no prerequisites stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools