Skip to main content
Glama

content_list

List course teaching materials, assignments, and files with titles, types, sections, text, and attachment links; filter by title or body keyword to retrieve full text.

Instructions

一门课的教学内容(含子文件夹):标题、类型(作业/项目/文件/内容文件夹…)、所在栏目、正文和附件链接。

不给 query 时正文只截前 300 字;按标题或正文关键词 query 过滤时返回完整正文。

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": "content_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNo
queryNo
refreshNo
course_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

B3.3/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. It does disclose one genuinely non-obvious behavior: without a query, body text is truncated to the first 300 characters, while title or body keyword filtering returns the complete body. It says nothing about permissions, pagination or result limits, ordering, or what refresh actually does to the underlying data.

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?

Two short paragraphs with no filler: the first states what is returned, the second states the query-dependent truncation rule. Content is front-loaded and every sentence carries information.

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

Completeness3/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-value shape need not be explained, and the truncation rule covers the main surprise. However, with zero annotation coverage and 0% parameter documentation, the meanings of kind and refresh remain unexplained, which is a real gap for a four-parameter listing tool.

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

Parameters2/5

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

Schema description coverage is 0%, so all four parameters depend on the description. Only query receives real semantic content, namely that it matches against title or body keywords and changes truncation behavior. kind (which presumably maps to the listed types), refresh, and even course_id's expected identifier format are left entirely 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?

The description uses a specific verb+resource: it lists a course's teaching content, explicitly including subfolders (含子文件夹), and enumerates the returned fields (title, type such as 作业/项目/文件/内容文件夹, section, body, attachment links). This distinguishes it reasonably from siblings like announcement_list or attachment_download, though it never names an alternative to route to.

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

Usage Guidelines3/5

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

Use is only implied: the description explains that omitting query yields truncated bodies while supplying a keyword query yields full bodies, which the reader can turn into a usage decision. There is no explicit when-to-use/when-not-to-use guidance, no statement about how this differs in purpose from assignment_list or course_list, and no prerequisites.

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