Skip to main content
Glama
Sign In
quercus-mcp

quercus-mcp

by lance-lii
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

List announcements

list_announcements

Read announcements for chosen courses by supplying their course IDs, helping you monitor official updates and due dates.

Instructions

List announcements for one or more courses (context_codes like 'course_12345').

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_ids": "<course_ids>"
    },
    "name": "list_announcements"
  }
}

Input Schema

NameRequiredDescriptionDefault
course_idsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden, yet it says nothing about being a read-only operation, authentication/permission requirements, pagination, result limits, or whether unpublished announcements are included. For a listing tool with zero annotation coverage this is a substantial gap.

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?

A single front-loaded sentence with no filler; the resource and scope come first. It is efficient, though the parenthetical format hint arrives slightly late in the sentence.

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?

With no output schema, no annotations, and a parameter whose schema documents nothing, the description should say more about return shape or pagination. For a simple one-parameter list tool it is minimally adequate but leaves real gaps.

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 clarify the required ID format ('context_codes like course_12345') and that multiple courses are accepted, which the bare 'array of strings' schema does not convey, but it leaves cardinality limits and matching behavior unexplained.

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?

States a specific verb (List) and resource (announcements) and adds scope ('for one or more courses'), so an agent knows exactly what is returned. It does not differentiate itself from siblings like list_courses or list_todo, though the resource noun is distinct enough that confusion is unlikely.

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

Usage Guidelines2/5

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

There is no statement of when to use this tool versus alternatives, no prerequisites (e.g. enrollment, permissions), and no exclusions. Usage is only inferable from the tool name and the plural-course scope.

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

Deploy Server

Other Tools