grandma2-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MA2_HOST | No | 目标主机 | 127.0.0.1 |
| MA2_USER | No | 登录用户 | administrator |
| MA2_PORTS | No | 候选 Telnet 端口 | 30000,30001 |
| MA2_TIMEOUT | No | 响应超时,单位秒 | 15 |
| MA2_PASSWORD | Yes | 登录密码,必填 | |
| MA2_OUTPUT_DIR | No | 日志、备份、导出和截图目录;安装 wheel 后建议显式设置 | 仓库 .data |
| MA2_ALLOW_WRITE | No | 设为 1 启用写入 | 0 |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| ma2_connectionsB | Connect onPC and MA3D simultaneously; return runtime identity, Show and session state for each. |
| ma2_statusA | Inspect one verified runtime: target is onpc or ma3d. Does not change the Show. |
| ma2_listB | List a native object/range, e.g. Executor 3.1 Thru 3.8 or Root 10.6.3; no command chains. |
| ma2_executeA | Execute up to 100 authorized commands sequentially; requires MA2_ALLOW_WRITE=1 and matching Show. Not transactional. Stops at first failure; prior commands may already be applied. Do not retry after a timeout without querying state. User scope still governs every command. |
| ma2_exportB | Export a local native object to unique XML and return a timestamp-independent fingerprint. |
| ma2_backupB | Save onPC Show, wait for asynchronous completion, copy a new backup and return SHA256. Write gate applies. |
| ma3d_transformA | Set x/y/z (metres), rx/ry/rz (degrees), or camera fov (radians), and return before/after List. Requires an inspected scene Root address or Camera number. Installation orientation is NOT programmed Pan/Tilt. MA3D edits can synchronize into onPC. Use target=onpc if its shared scene is the intended authority. Requires write gate and expected Show; no visual pass is implied. |
| ma3d_captureA | Save the uniquely identified visible local MA3D window as PNG, without UI input. Windows only. Read the returned image to inspect the camera and beams. Does not start playback, select Front, or certify visual acceptance. Minimized/blank/ambiguous windows fail. |
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 8 tools
Most tools have a clearly distinct action (list, execute, export, backup, transform, capture). The one weak pair is ma2_connections vs ma2_status, since both return runtime identity and Show/session state and differ mainly by whether a connection is established — an agent could reasonably pick the wrong one.
Names are uniformly snake_case with a useful ma2_/ma3d_ subsystem prefix, making scope obvious at a glance. Minor deviation: some are verbs (list, execute, export, backup, transform, capture) while others are nouns (connections, status).
Eight tools is well-scoped for a console/visualizer control surface: connection, inspection, listing, command execution, export, backup, 3D transform, and capture. Each earns its place with no filler.
Core lifecycle is covered: connect, inspect, read state, write commands, export, back up, manipulate 3D scene, and capture visuals. Gaps remain around disconnect, cancelling/aborting a hung execute, and reading command feedback or history, which agents may need after partial failures.