Skip to main content
Glama

List rubrics

bb_list_rubrics
Read-only

Retrieve all rubrics for a specified course ID to review grading criteria and assessment expectations.

Instructions

List rubrics available in a course.

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": {
      "courseId": "<courseId>"
    },
    "name": "bb_list_rubrics"
  }
}

Input Schema

NameRequiredDescriptionDefault
courseIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds only the course-scoping constraint and says nothing about result volume, pagination, ordering, or the permissions needed to view rubrics, so it contributes little beyond the structured fields.

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 short sentence with the resource and scope front-loaded and no filler. It is efficient, though its brevity borders on under-specification rather than being genuinely concise.

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?

For a simple read-only, single-parameter list tool this covers the basic purpose, and annotations carry the safety profile. With no output schema, however, the description omits any hint of what a rubric entry contains or whether the list is truncated, leaving real gaps for an agent planning a call.

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% and the single courseId parameter is typed only as a bare string. The description implies courseId identifies the course, but does not clarify the ID format or whether it accepts a course system ID versus another identifier, so it fails to compensate for the coverage gap.

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 ('List') plus a specific resource ('rubrics') and adds scope ('available in a course'), so an agent knows exactly what is returned. It does not, however, distinguish itself from related siblings such as bb_attach_rubric or bb_get_assignment_context, so it stops short of a 5.

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 guidance on when to call this versus alternatives (e.g. attaching a rubric, or listing other course resources). The only usage signal is the implied 'you need rubrics for a course', with no preconditions, exclusions, or named alternatives.

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