Skip to main content
Glama

Read full assignment context

bb_get_assignment_context
Read-only

Retrieves assignment instructions, submission and scoring status, files, posted links, rubric associations, and related announcements in one call to review context before grading or submitting.

Instructions

Return assignment instructions, scoring/submission status, available files, posted links, rubric associations when exposed, and related announcements in one call. Read files with bb_get_attachment.

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>",
      "contentId": "<contentId>"
    },
    "name": "bb_get_assignment_context"
  }
}

Input Schema

NameRequiredDescriptionDefault
courseIdYes
contentIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=true), so the description's value lies elsewhere. It does add real behavioral detail by enumerating the return contents in the absence of an output schema, and the qualifier 'when exposed' honestly flags that rubric associations are conditionally present. It stops short of noting course enrollment requirements or behavior on invalid IDs.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, zero filler: the payload enumeration comes first and the single follow-up routing hint second. Nothing is repeated from the schema or annotations.

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 an aggregation read with no output schema, listing the returned sections is genuinely the right move and is done well. However, with 0% schema coverage and a sibling set that includes bb_get_assignment and bb_get_assignment_submission, the definition leaves the agent guessing about the identifier semantics and about what this tool does NOT return.

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 both parameters (courseId, contentId) are required with no documentation anywhere. The description compensates only implicitly by saying 'assignment context', leaving ambiguous whether contentId is an assignment identifier or a generic content-item identifier shared with siblings like bb_get_content.

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 names a specific verb and resource (Return ... assignment context) and enumerates the payload: instructions, scoring/submission status, files, links, rubric associations, announcements. This is far more specific than the title alone, though it never contrasts with the sibling bb_get_assignment, so an agent must infer that this is the aggregate view rather than the metadata-only view.

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 implied rather than stated: 'in one call' signals it should be preferred over multiple fetches, and 'Read files with bb_get_attachment' explicitly routes one follow-up step to a sibling. There is no explicit when-not guidance or statement of what this tool omits relative to bb_get_assignment or bb_get_assignment_submission.

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