Skip to main content
Glama
shibig666

QMYZ-MCP

by shibig666
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

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

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

Tools

Functions exposed to the LLM to take actions

NameDescription
get_coursesC

获取课程名称与ID

参数:
    JSESSIONID (str): 用户的JSESSIONID
get_questionC

获取课程题目

参数:
    JSESSIONID (str): 用户的JSESSIONID
    course_id (str): 课程ID
submit_questionC

提交课程题目答案, 返回答题结果。提交的answer应为选项的字母，例如 "A" 或 "B"

参数:
    JSESSIONID (str): 用户的JSESSIONID
    course_id (str): 课程ID
    question_id (str): 题目ID
    answer (str): 答案，例如 "A" 或 "B" 等选项

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

B3.3/5.0

Scored across 3 tools

Disambiguation5/5

Each tool has a clearly distinct purpose: get_courses retrieves course metadata, get_question fetches questions for a specific course, and submit_question submits answers to specific questions. There is no overlap in functionality, and the descriptions clearly differentiate their roles in the workflow.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern with snake_case (get_courses, get_question, submit_question). The naming is predictable and readable, making it easy for agents to understand the action each tool performs.

Tool Count3/5

With only 3 tools, the server feels thin for a course/quiz management domain. While the tools cover core operations, additional functionalities like updating courses or managing user sessions might be expected. However, the count is not critically low, just borderline minimal.

Completeness4/5

The toolset covers a basic workflow: list courses, get questions, and submit answers. Minor gaps exist, such as no tools for creating or deleting courses, or handling user authentication beyond JSESSIONID. Agents can work around these, but the surface is not fully comprehensive for the domain.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources