Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
WOP_KEYS_DIRNo私钥落盘目录(0600 文件)./keys
WOP_DOC_BASE_URLNo文档中心基址https://assets.wanlianyida.com/gtsp/platformResource/wop/doc-center
WOP_HTTP_TIMEOUTNoHTTP 超时秒数15
WOP_INDEX_CACHE_TTLNollms.txt 索引进程内缓存秒数(0 关闭)300

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

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
wop_overviewA

获取万联易达开放平台(WOP)的接入指南与全部 API 索引。

内容包含:三步接入流程、securityReq 算法组合、公钥分发编码、官方 SDK 与
工具列表,以及实时拉取的 llms.txt API 索引(按业务域分组)。
索引中的 API 可用 wop_api_detail 进一步获取详情,链接可用 wop_link_detail 获取。

Returns:
    str: 接入指南 + API 索引(markdown 格式)
wop_api_detailA

获取万联易达开放平台(WOP)指定 API 接口的详细定义。

支持三种入参形态(按优先级):
1. API 路径:如 /staffing/open/v1/invoice/apply(可带 POST/GET 前缀,
   支持省略业务域前缀的后缀匹配)
2. 接口中文名:如 转账提交
3. 完整 .md URL:直通下载

匹配到多个接口时返回候选列表,请用更精确的路径或 URL 重试。

Args:
    api: str - API 路径、接口中文名或完整 .md URL

Returns:
    str: API 接口详情(markdown 格式:基本信息、请求参数、响应参数、示例等)
wop_link_detailA

获取万联易达开放平台(WOP)文档中心子页面或外部链接的详细内容。

接受完整 URL,或文档中心相对路径(自动拼接文档中心基址,
如 staffing/api/staffing/open/v1/invoice/apply.2026….md 或 llms-full.txt)。

Args:
    url: str - 完整 URL 或文档中心相对路径

Returns:
    str: 页面内容(markdown 格式)
wop_gen_key_pairA

生成 WOP 对接所需的非对称密钥对(RSA2048 / SM2)。

安全纪律:私钥只写入本地 0600 文件,不会出现在返回值或对话中;
返回的 publicKey 为分发契约编码(RSA:SPKI DER Base64;
SM2:未压缩点 04‖X‖Y Base64),可直接上报平台。

Args:
    algorithm: str - "RSA2048"(别名 "RSA")或 "SM2",默认 "RSA2048"

Returns:
    Dict 包含 algorithm / publicKey / privateKeyFile(路径) / message

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.1/5.0

Scored across 4 tools

Disambiguation4/5

wop_overview and wop_gen_key_pair are clearly distinct, and wop_api_detail targets API definitions while wop_link_detail targets documentation pages. However, both detail tools accept URLs, so an agent could confuse which one to use for a given link despite the descriptions clarifying intent.

Naming Consistency4/5

All tools use a consistent wop_ prefix and snake_case, which makes the set predictable. The only minor deviation is that wop_gen_key_pair uses a verb phrase while the other three are noun-oriented, but the pattern remains readable.

Tool Count5/5

Four tools are well-scoped for a WOP integration server: one provides onboarding/index, two retrieve specific docs or API details, and one generates required key pairs. Each tool earns its place without redundancy or excessive surface area.

Completeness4/5

The server covers the core WOP integration lifecycle: overview/index, API detail lookup, documentation link retrieval, and key generation. Minor gaps exist, such as no standalone search across APIs or direct SDK download tool, but the overview and link tools provide workarounds.

Maintenance

ActivityMaintained
ResponsivenessNo issues