Skip to main content
Glama

get_exercises

Fetch course exercises with availability windows and attempt status to see which quizzes are open and if the student has attempted them.

Instructions

Exercises (quizzes) of a course with their availability window and whether the student has attempted them.

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": {
      "course": "<course>"
    },
    "name": "get_exercises"
  }
}

Input Schema

NameRequiredDescriptionDefault
courseYes

Output Schema

NameRequiredDescriptionDefault
resultYes

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?

No annotations are supplied, so the description carries the burden; it does disclose that results include the availability window and whether the student attempted each exercise, which tells the agent the data is per-student and time-scoped. It does not state permissions, access restrictions (e.g., enrolled students only), or ordering, leaving real behavioral gaps for an unannotated tool.

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 resource is named first and the return highlights follow. It is appropriately sized, though the parenthesis-heavy phrasing is slightly dense.

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?

An output schema exists, so return values need not be spelled out, and a one-parameter read tool is low complexity. Still, the definition omits the course-identifier format and any access prerequisites, which an agent needs before a first successful call.

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 'course' parameter, so the description compensates only partially by indicating the course scopes the exercise list. It never says whether the identifier is a course ID, code, or name, so the format ambiguity 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?

Names a specific resource ('Exercises (quizzes) of a course') and clarifies the parent term exercises as quizzes, which disambiguates it from get_assignments and get_deadlines. It stops short of explicitly contrasting with those siblings, so it is clear but not fully differentiated.

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 or when-not-to-use guidance and no mention of alternatives such as get_assignments for graded work. The agent must infer that this is the tool for quiz/exercise listings within a single course.

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