Skip to main content
Glama

Get assignment submissions

bb_get_assignment_submission
Read-only

Retrieves assignment attempts and submission files for a gradebook column, showing students their own attempts and instructors all attempts.

Instructions

List attempts and submission files on a gradebook column. Students see their own attempts; instructors see every attempt.

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

Input Schema

NameRequiredDescriptionDefault
columnIdYes
courseIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/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 genuinely new behavior: results are scoped by the caller's role, which an agent could not infer from the schema. It stops short of describing return shape, pagination, or whether an ungraded/empty column yields an empty list.

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, the resource is front-loaded, and neither sentence is filler. The phrase 'attempts and submission files' is slightly ambiguous about whether these are two separate result types, which a couple more words could resolve.

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 two-parameter list tool with no output schema, the description covers what is listed and who sees what, but omits the return structure and ordering/pagination behavior that an agent needs to use results correctly. It is adequate but leaves clear gaps against the tool's actual complexity.

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 the description must carry both parameters. It ties columnId to 'a gradebook column', which is helpful, but courseId is never mentioned and no format or ID expectations are given for either. Half the parameter meaning is left to inference.

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 gives a concrete verb and resource: 'List attempts and submission files on a gradebook column.' That is specific enough to separate it from bb_get_assignment (assignment metadata) and bb_get_attempt (a single attempt). It does not explicitly name those siblings, so differentiation is inferred rather than stated.

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?

The second sentence explains visibility scope by role (students see own attempts, instructors see all), which is useful context but not when-to-use guidance. There is no statement of when to prefer bb_get_attempt or bb_get_assignment instead, and no prerequisites or exclusions.

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