Skip to main content
Glama

Niche of One Network

Submit a course exercise

course_submit
Idempotent

Members. Mark a Method lesson done after its exercise. The answer is not stored; only that the lesson is done. Shows what it will record first; call again with confirm true.

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": {
      "lesson": "<lesson>",
      "answer": "<answer>"
    },
    "name": "course_submit"
  }
}

Input Schema

NameRequiredDescriptionDefault
answerYes
lessonYes
confirmNoLeave out to preview; true to commit.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare the write profile (readOnlyHint=false, destructiveHint=false, idempotentHint=true), so the bar is lower. The description still adds real value by disclosing that the answer is not persisted and that a preview precedes the commit. It does not say what the preview returns or what happens if confirm is passed without a prior preview.

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?

Three short sentences with the critical facts front-loaded: what gets recorded, what does not, and how to commit. The leading "Members." fragment is the only wasted or unclear text; everything else earns 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 3-parameter mutation tool with no output schema and no annotation-level detail beyond safety hints, the definition covers the preview/commit flow and the discarded answer. It is still silent on the return value of the preview call and on the meaning of the lesson identifier, leaving gaps an agent must guess at.

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 only 33%, with just confirm documented in the schema. The description compensates partially by explaining that the submitted answer is discarded, which is the most important semantic for the answer parameter. However, the lesson parameter — an integer 1-999, presumably a lesson ID — is never explained in either place.

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: marking a Method lesson done after its exercise, with the answer discarded. That is more precise than the title alone, though the opening fragment "Members." is opaque and the pointer to which sibling (course/academy_lesson) is being complemented is left implicit.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It states the trigger condition (after completing the lesson's exercise) and gives explicit invocation guidance for the two-step flow: preview first, then call again with confirm true. It does not explicitly exclude alternatives such as browsing lessons via academy_lesson, but the usage context is clear enough to act on.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources