Skip to main content
Glama
cfrs2005

GS Robot MCP Server

by cfrs2005

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
GS_CLIENT_IDYesYour Gausium Application Client ID
GS_CLIENT_SECRETYesYour Gausium Application Client Secret
GS_OPEN_ACCESS_KEYYesYour Gausium OpenAPI Access Key

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
list_robotsD

列出机器人 / List robots

get_robot_statusD

查询机器人状态 / Get robot status

describe_work_stateC

解释工作状态 / Describe robot work state

get_robot_capabilitiesC

查询机器人任务能力 / Get task capabilities

list_robot_mapsC

列出机器人地图 / List robot maps

get_map_canvasD

查询地图画布 / Get map canvas

list_charging_positionsC

列出充电点 / List charging positions

list_map_resourcesD

列出地图资源 / List map resources

list_task_resourcesD

查询任务资源 / List task resources

list_work_modesD

查询工作模式 / List work modes

list_task_definitionsC

分页查询任务定义 / List task definitions

get_task_definitionD

查询任务定义 / Get task definition

create_task_definitionD

创建任务定义 / Create task definition

update_task_definitionD

更新任务定义 / Update task definition

delete_task_definitionD

删除任务定义 / Delete task definition

start_taskD

启动任务 / Start task

pause_taskC

暂停任务 / Pause task

resume_taskD

继续任务 / Resume task

stop_taskD

停止任务 / Stop task

skip_task_itemD

跳过任务项 / Skip task item

create_simple_scheduleD

创建简易排班 / Create simple schedule

update_simple_scheduleD

更新简易排班 / Update simple schedule

delete_simple_scheduleD

删除简易排班 / Delete simple schedule

create_scheduleD

创建标准排班 / Create schedule

update_scheduleD

更新标准排班 / Update schedule

delete_scheduleD

删除标准排班 / Delete schedule

list_schedulesD

列出排班 / List schedules

get_scheduleD

查询排班详情 / Get schedule

get_schedule_calendarC

查询月度排班 / Get schedule calendar

list_schedule_pre_tasksC

查询每日预任务 / List schedule pre-tasks

get_command_statusC

查询命令投递状态 / Get command delivery status

list_command_historyD

查询命令历史 / List command history

navigate_homeC

导航回充电点 / Navigate home

pause_navigationC

暂停导航 / Pause navigation

resume_navigationC

继续导航 / Resume navigation

stop_navigationC

停止导航 / Stop navigation

list_task_reportsC

分页查询任务报告 / List task reports

get_task_report_map_imagesD

查询报告地图图像 / Get report map images

lookup_error_codeB

查询错误码含义与处置(本地码表与调用经验)/ Look up an error code's meaning and handling in the local reference tables

rememberA

把一条经证实的可复用经验写入本地记忆(需用户确认)/ Save one verified, reusable lesson to local memory (needs user approval)

wait_for_commandC

等待命令投递终态 / Wait for command delivery

run_cleaning_taskC

创建并启动清洁任务 / Create and start cleaning task

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

C2.2/5.0

Scored across 42 tools

Disambiguation3/5

Many tools are distinct, but the simple-vs-standard schedule variants (create_simple_schedule vs create_schedule, etc.) are easy to confuse, and run_cleaning_task overlaps with create_task_definition plus start_task. Task, report, resource, and work-mode listing tools also have subtle boundary differences that descriptions only partially clarify.

Naming Consistency4/5

Most names follow a consistent snake_case verb_noun pattern, such as list_robots, get_robot_status, create_task_definition, and stop_navigation. A few outliers like remember and wait_for_command are slightly less predictable, but the overall convention is stable.

Tool Count2/5

With 42 tools, the surface is heavy for the apparent robot-management domain and exceeds the typical well-scoped range. The duplication of simple and standard schedule CRUD operations makes the set feel bloated rather than tightly scoped.

Completeness4/5

The server covers robot status, maps, task definitions and execution, reports, schedules, navigation control, command tracking, error lookup, and memory, which is broad lifecycle coverage. Minor gaps remain, such as no arbitrary point-to-point navigation tool, but core robot operations are well represented.

Maintenance

ActivityMaintained
ResponsivenessNo issues