Skip to main content
Glama

Get attempt detail

bb_get_attempt
Read-only

Retrieve a specific submission attempt with its files, receipt, and submission text to review student work or submission status.

Instructions

Get one submission attempt, including files, receipt and submission text.

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>",
      "attemptId": "<attemptId>"
    },
    "name": "bb_get_attempt"
  }
}

Input Schema

NameRequiredDescriptionDefault
courseIdYes
attemptIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already establish readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds payload context — that the response bundles files, receipt, and submission text — which is genuinely useful for deciding whether to call it. It says nothing about permissions (e.g., needing to be the student or an instructor) or size/pagination of the returned files.

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 no filler; the resource and returned contents come first and nothing is wasted.

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 read-only annotations and no output schema, the description gives enough to know what comes back but leaves the parameters entirely unexplained. Enough to act on if the agent already knows the IDs, but not self-sufficient.

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?

Both parameters (courseId, attemptId) are required and schema description coverage is 0%, so the description carries the full burden — yet it mentions neither parameter, their format, nor where an attemptId comes from. The baseline would be 3 only if the schema documented the fields; it does not.

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 submission attempt') and enumerates what the result contains (files, receipt, submission text), which helps distinguish it from the many other 'get' siblings. It never explicitly contrasts itself with, e.g., bb_get_assignment_submission, so differentiation is implicit 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?

The description contains no when-to-use guidance, no prerequisites, and no mention of an alternative tool for retrieving submissions. An agent must infer from the name alone that this requires a known attemptId, presumably obtained from a submission endpoint.

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