Skip to main content
Glama

Get my grades

bb_get_my_grades
Read-only

Retrieve your grades for a specified course, including points possible and submission status, so you can check your performance and pending work.

Instructions

Return your grades for one course, with points possible and submission state.

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

Input Schema

NameRequiredDescriptionDefault
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 useful return-content context ('points possible and submission state'), but leaves open whether this is strictly the caller's own enrollment, whether ungraded items appear, and whether results are paginated — and there is no output schema to fill those gaps.

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?

A single front-loaded sentence with no filler; the scope and return contents are stated up front. It is efficient but so terse that it omits routing information that would have earned its place.

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 one-parameter read tool with annotations covering safety, the description is close to sufficient: it says what is returned and for what scope. What is missing is how to source the courseId and what 'your' means for a teacher or observer role, which matters given no output schema exists.

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% for the single courseId parameter, so the schema supplies only a bare string type. The description partially compensates by establishing that the value selects one course, but gives no format, source, or example for the identifier, leaving the agent to guess how to obtain a valid courseId.

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 your grades') and scopes it to a single course, so the agent knows it is a per-course grade lookup rather than a full gradebook dump. It does not explicitly contrast with siblings like bb_get_gradebook or bb_get_assessment, 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 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: nothing says when to prefer this over bb_get_gradebook for an all-course view or over bb_get_assessment for a single item's detail. The only implied signal is 'one course', which an agent must extrapolate from the parameter.

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