Skip to main content
Glama

List gradebook attempts

bb_list_column_attempts
Read-only

List attempts on a gradebook column so students can view their own submissions and instructors can review all student attempts for grading.

Instructions

List attempts on a gradebook column. Students see their own; instructors see all students.

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>",
      "columnId": "<columnId>"
    },
    "name": "bb_list_column_attempts"
  }
}

Input Schema

NameRequiredDescriptionDefault
columnIdYes
courseIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/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 the safety profile is covered. The description adds real value by disclosing role-based result scoping (students see their own attempts, instructors see all students'), which affects how the agent should interpret results. It says nothing about ordering, pagination, or behavior for an empty or invalid column.

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 the resource scope front-loaded and zero filler. It is efficient, though the second sentence is a caveat rather than the primary action, which slightly weakens front-loading.

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 two-parameter read tool with no output schema, the description covers purpose and result scoping but leaves parameter formats and result shape unexplained. Adequate as a minimum, with clear gaps given 0% schema coverage.

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% for two required parameters. The description implies columnId via 'gradebook column' but never mentions courseId and gives no ID formats or scoping rules, so it does not compensate for the documentation 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 states a specific verb and resource: listing attempts scoped to a single gradebook column. That is clearly distinct from bb_get_gradebook (which would return the gradebook structure itself), so an agent can tell them apart, though no sibling is named explicitly.

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 explicit when-to-use or when-not-to-use guidance, and no alternative is named. The role-visibility sentence hints at what results look like per caller but does not help the agent decide between this tool and related listing tools.

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