Skip to main content
Glama

Get assessment settings

bb_get_assessment
Read-only

Retrieve a single assessment by course and gradebook column ID, returning the gradebook column plus linked content and available questions for review.

Instructions

Get one assessment (gradebook column + linked content + questions when available).

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

Input Schema

NameRequiredDescriptionDefault
columnIdYes
courseIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/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 a meaningful behavioral detail: questions are included only 'when available,' signaling a conditionally shaped response. It does not say what happens when the column id is unknown or whether linked content can be missing.

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?

A single front-loaded sentence with a compact parenthetical that enumerates the response parts. Every clause adds information; there is no filler or repetition of the title.

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 read tool with annotations and no output schema, the description covers the general return composition but leaves the shape and conditional cases underspecified. It is minimally adequate rather than complete.

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?

Schema description coverage is 0%, so the description must carry meaning, and it does partially by tying 'columnId' to the gradebook column concept. It still gives no format or identifier guidance for courseId or columnId (string types, expected shapes), so a substantial gap remains.

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?

States a specific verb and resource ('Get one assessment') and disambiguates the payload by enumerating what an assessment comprises: gradebook column, linked content, and questions when available. This separates it from bb_get_assignment or bb_get_gradebook, though it never explicitly names those alternatives.

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 when-to-use guidance, no statement of prerequisites, and no routing to alternatives such as bb_get_gradebook or bb_get_assignment. The only implied usage is that you fetch a single assessment by course and column, which the agent must infer from the parenthetical.

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