Skip to main content
Glama

sis_cart

Retrieve Westlake SIS course cart contents, including courses, credits, and status, without making enrollment changes or write operations.

Instructions

取 SIS 选课车内容(课程 / 学分 / 状态;只读,不做选课写操作)。

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "sis_cart"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations supplied, the description carries the full burden, and it does disclose the most important trait: the operation is read-only and performs no enrollment writes. It says nothing about authentication requirements, empty-cart behavior, or freshness of the cart state, which are relevant for a session-dependent read.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single compact sentence: verb plus resource first, then the returned fields, then the read-only scope constraint. Nothing is redundant and nothing needed to be moved forward.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-parameter read tool with no output schema and no annotations, the description covers purpose, returned content, and the read-only guarantee, which is enough to call it correctly. A note on what an empty or unavailable cart returns would close the remaining gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so the baseline is 4; there is no parameter meaning for the description to add or omit. The field list in the description instead describes output content, which is a sensible use of the space.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource (取 SIS 选课车内容) and enumerates the returned fields (课程 / 学分 / 状态), so the agent knows exactly what this tool yields. It does not, however, name the sibling tools (e.g. sis_registration) that handle the write-side enrollment that this tool explicitly excludes.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The parenthetical '只读,不做选课写操作' gives a clear when-not boundary: this is for viewing the cart, not for enrolling, which steers the agent away from using it for write tasks. The gap is that it never names the alternative tool that does perform enrollment, leaving that routing to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.