AgentSkills MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TAVILY_API_KEY | No | API key for Tavily web search | |
| FLOW_LLM_API_KEY | Yes | API key for OpenAI-compatible LLM service | |
| DASHSCOPE_API_KEY | No | API key for DashScope search and entity extraction | |
| FLOW_LLM_BASE_URL | Yes | Base URL for OpenAI-compatible LLM service | |
| TUSHARE_API_TOKEN | No | API token for Tushare historical data analysis | |
| BAILIAN_MCP_API_KEY | No | API key for external MCP services |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| load_skill_metadataB | Load metadata (name and description) for all available skills from the skills directory. |
| load_skillC | Load one skill's instructions from the SKILL.md. |
| read_reference_fileC | Read a reference file from a skill (e.g., forms.md, reference.md, ooxml.md) |
| run_shell_commandC | run shell command in a subprocess.
Here you need to fill in skill_name.
This skill_name parameter allows you to navigate directly to the folder corresponding to skill_name, making it more convenient to use the scripts within that folder to execute commands.
If you want to know the exact path, you can use |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
The tools have mostly distinct purposes with clear boundaries: loading skill instructions, loading skill metadata, reading reference files, and running shell commands. However, there is some potential for confusion between load_skill and load_skill_metadata, as both involve loading skill-related data but target different aspects (full instructions vs. metadata).
All tool names follow a consistent verb_noun pattern with snake_case throughout (load_skill, load_skill_metadata, read_reference_file, run_shell_command). The naming is predictable and readable without any deviations in style or convention.
With 4 tools, the count is well-scoped for the server's purpose of managing agent skills. Each tool serves a distinct function (loading, reading, executing) that covers essential operations without being excessive or insufficient for the domain.
The tool set covers core operations like loading skills and running commands, but there are notable gaps. For example, there are no tools for creating, updating, or deleting skills, which limits full lifecycle management. The surface is functional for basic tasks but incomplete for comprehensive skill handling.