openaaas-mcp-adapter
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": true
} |
| resources | {
"subscribe": false,
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| discoverC | 发现服务端 API 信息 |
| set_server_urlC | 设置服务器地址并保存到配置文件 |
| registerB | 注册客户端账号，获取 api_key（仅需一次） |
| update_profileC | 修改当前客户端用户名 |
| list_servicesC | 获取可用的 Agent 服务列表（轻量摘要） |
| get_service_usageB | 获取指定服务的详细用法说明（能力范围、调用规范、返回格式、限制条件） |
| submit_taskC | 提交任务到远程 Agent（支持文件上传） input_files 为本地文件路径列表，只能上传当前工作目录下的文件，单个文件不超过 100MB。 |
| get_taskB | 查询任务状态和最终结果（仅在用户明确要求时调用） ⚠️ 不要主动轮询。只有在用户明确要求查询任务状态时，才调用此工具。 |
| poll_taskA | 轮询任务直到获得最终结果（仅用户明确要求时使用） 每 20 秒查询一次任务状态，直到任务进入 completed / failed / cancelled 状态。 默认不设置超时；传入 timeout_seconds 可限制最大轮询时长。 ⚠️ 重要：Agent 禁止主动调用此工具。ONLY use this tool when the user explicitly asks to wait for or poll a task result (e.g. "帮我等结果"、"轮询一下任务"). 如果用户没有明确表达等待意图，应询问用户而不是直接轮询。 |
| cancel_taskC | 取消执行中的任务 |
| list_filesC | 列出任务的结果文件 |
| download_resultB | 下载任务结果文件并返回每个文件的完整路径
返回结果中会明确列出每个文件的完整路径，读取文件时请直接使用这些路径，不要推测子目录。 |
| list_serversB | 列出所有已配置的服务器 |
| set_default_serverC | 切换默认服务器 |
| remove_serverB | 删除指定服务器的配置（不能删除默认服务器） |
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 15 tools
Most tools target clearly distinct resources or actions: server config, client registration, service discovery, task lifecycle, and file handling. The main overlap is get_task versus poll_task, since both retrieve task status/results, though their descriptions distinguish one-shot queries from explicit polling.
Names are consistently snake_case and mostly follow a verb_noun pattern such as list_services, submit_task, and download_result. Minor deviations are discover and register, which use bare verbs, but the set remains predictable and readable.
The 15 tools are well-scoped for an adapter covering server configuration, client setup, service discovery, task execution, and result file access. Each tool has a plausible role, and the count fits within a reasonable range for the domain.
The surface covers the main lifecycle: configure servers, register a client, inspect services, submit and monitor tasks, cancel tasks, and list/download result files. Minor gaps exist, such as no explicit task history/list operation or profile retrieval, but core workflows are covered.