Skip to main content
Glama

Get gradebook

bb_get_gradebook
Read-only

Retrieve gradebook columns and your own course grades; instructors also get every column and its scoring settings.

Instructions

Return gradebook columns plus your own grades for a course. Instructors also see every column and its scoring settings.

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_get_gradebook"
  }
}

Input Schema

NameRequiredDescriptionDefault
courseIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds genuinely useful role-dependent behavior ('Instructors also see every column and its scoring settings'), but says nothing about behavior for non-enrolled users, empty gradebooks, or result size/pagination.

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?

Two short sentences with no filler, and the primary payload is front-loaded before the role caveat. Nothing is redundant, though the second sentence could be integrated more tightly.

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 one-parameter read-only tool with no output schema, the description covers what comes back (columns plus own grades) and how that varies by role. Only minor gaps remain, such as error conditions and result volume.

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?

There is a single parameter (courseId) with 0% schema description coverage, so the schema adds no meaning. The phrase 'for a course' confirms the parameter is a course identifier but gives no format, source, or example, leaving the description short of full compensation.

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 opens with a concrete verb and resource ('Return gradebook columns plus your own grades for a course'), making the payload clear. It implicitly separates itself from a learner-wide view via 'for a course', but never names a sibling such as bb_get_my_grades or bb_get_assessment, so differentiation is left to inference.

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?

Usage is only implied: an agent can infer this is the per-course gradebook read. There is no explicit when-to-use statement, no mention of when bb_get_my_grades or bb_get_assessment would be the better pick, and no stated prerequisites such as enrollment or instructor role.

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