e签宝 MCP Server
OfficialServer 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 |
|---|---|
| create_sign_flowB | 创建签署流程，支持多种文件格式，包括：PDF、Word、Excel、PPT、WPS、图片等。非PDF格式会自动转换为PDF。 |
| query_sign_flowC | Query sign flow details |
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: create_sign_flow initiates a signing process, while query_sign_flow retrieves details about an existing one. There is no overlap in functionality, making it easy for an agent to choose the correct tool based on the task.
Both tools follow a consistent verb_noun pattern with snake_case: create_sign_flow and query_sign_flow. The naming is predictable and aligns well with their respective actions, ensuring clarity and uniformity.
With only two tools, the server feels under-scoped for an e-signature domain, which typically requires operations like updating flows, canceling, downloading documents, or managing templates. This limited set may hinder agents from completing common workflows.
The tool surface is severely incomplete for e-signature functionality. It lacks essential operations such as updating or canceling flows, downloading signed documents, and managing templates or signers. Agents will face significant gaps in handling full signing lifecycles.