Skip to main content
Glama
Sign In
Codemm

Codemm

by iignaite
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_exercise

Show a learner the current or specified exercise, including statement, files to edit, visible tests, and hint—or quiz questions and choices without answers.

Instructions

Show an exercise to the learner: statement, the file(s) to edit, visible tests and hint; for a quiz, its questions and choices, never the key.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_exercise"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugNoExercise id. Defaults to the current exercise.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose meaningful behavior beyond structure: it enumerates the returned payload and adds the security-relevant constraint that a quiz's answer key is never exposed. It does not state error behavior for an unknown slug or confirm read-only semantics explicitly, though "Show" implies a pure read.

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?

One dense sentence with the primary payload listed first and the quiz variant and its exclusion clause second. Every clause carries information; there is no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple getter with no output schema and no annotations, the description compensates well by describing the return shape and the answer-key exclusion. The remaining gap is edge-case behavior, such as what happens when the slug is invalid or the exercise is locked.

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?

There is a single optional parameter and schema coverage is 100%, with the schema already documenting that slug defaults to the current exercise. The description adds nothing about the slug, so the baseline 3 applies.

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 ("Show") and resource ("exercise") and enumerates exactly what the learner sees: statement, files to edit, visible tests, hint, and quiz questions/choices. The resource word alone separates it from get_lesson and get_roadmap, but it never explicitly routes the agent away from those siblings.

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 only implied: this is the read path for a single exercise, in contrast to the save_exercise/check siblings, but the description never says when to call it versus get_lesson or next_step. The default-to-current-exercise behavior lives in the schema, not the description.

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

Deploy Server

Other Tools