MCP-FEISHU
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 |
|---|---|
| get_defect_linkD | – |
| get_recently_updated_defect_listD | – |
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 2 tools
The two tools have clearly distinct purposes: one retrieves a specific defect link, while the other fetches a list of recently updated defects. There is no overlap or ambiguity between them.
Both tools follow a consistent verb_noun pattern with 'get_' prefix and snake_case naming. The naming is predictable and uniform across the set.
With only 2 tools, the server feels thin for a domain like defect management in Feishu. This minimal set lacks essential operations like creating, updating, or deleting defects, making it under-scoped.
The tool surface is severely incomplete for defect management. It only provides read-only access to defects (link and list), missing critical CRUD operations such as create, update, delete, or search, which will cause agent failures in handling defect workflows.