Skip to main content
Glama

course_hide

Mark a course as dropped or not followed locally so assignments, announcements, and semester views skip it by default without changing the teaching site. Set hidden=false to undo.

Instructions

在本机把一门课标为退课/不关注(hidden=false 取消)。作业、公告和学期整理默认跳过它;不修改教学网。

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "course_id": "<course_id>"
    },
    "name": "course_hide"
  }
}

Input Schema

NameRequiredDescriptionDefault
hiddenNo
course_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A3.9/5.0
Behavior4/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 does useful work: it discloses the downstream effects (作业、公告和学期整理默认跳过), the reversibility mechanism (hidden=false), and critically that nothing is written to the teaching website. It does not cover error behavior for an unknown course_id, idempotency, or auth requirements.

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

Conciseness4/5

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

One dense sentence front-loaded with the action and scope, followed by effects and the non-modification guarantee. Nothing is wasted, though the inline parenthetical "(hidden=false 取消)" interrupts the flow slightly and could be a separate clause.

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?

An output schema exists, so return values need not be explained, and the tool is a simple two-parameter toggle. The description covers side effects, reversibility, and local-only scope; only course_id sourcing and failure modes are left open, which is a modest gap for a tool of this complexity.

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

Parameters3/5

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

Schema description coverage is 0%, so the description must compensate. It does explain the semantics of `hidden` including how to undo it (hidden=false 取消), which is genuinely beyond the schema, but course_id receives no guidance at all — no format, source, or example — leaving one of two parameters undocumented.

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?

"在本机把一门课标为退课/不关注" gives a specific verb (mark as dropped/unfollowed), a specific resource (a course), and an explicit scope boundary (local only, 不修改教学网). That local-vs-remote distinction is what separates it from server-side siblings like semester_sync or course_list, though no sibling is named outright.

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 description makes the use case concrete — hiding a course so assignments, announcements, and semester sync skip it by default — and gives the inverse operation (hidden=false 取消). It stops short of naming an explicit alternative tool or stating prerequisites such as auth_setup, so it is clear context without full routing guidance.

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