Skip to main content
Glama
Sign In

LearnWorlds MCP Server and API by Cotlet

by dev.cotlet
OverviewDiscussionsAdmin

Grade assessment in LearnWorlds

learnworlds_grade_assessment
Read-onlyIdempotent

Grade assessment in the user's own LearnWorlds account from ChatGPT, Claude or any AI agent. Returns how to do it in LearnWorlds step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's LearnWorlds Cloud Browser. LearnWorlds's official API: LearnWorlds has a REST API (v2) for courses, users, bundles, subscriptions, promotions, payments and certifications, but it comes with the Learning Center plan and higher, and you need your own code to use it (checked 5 Nov 2026).

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": "learnworlds_grade_assessment"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

The key disclosure — 'opens nothing by itself' — tells the agent this tool only returns guidance and performs no mutation, which is consistent with readOnlyHint=true and destructiveHint=false. The return content (screens, buttons, fields) is described, which the annotations cannot convey. It does not describe response length or failure modes, so it stops short of a 5.

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?

The core behavior and the browser hand-off are front-loaded in the first two sentences. The closing note on LearnWorlds's REST API is somewhat tangential and carries a dated verification stamp, but it does earn its place by explaining why browser automation is the route rather than the API.

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 zero-parameter, read-only guidance tool with no output schema, the description covers what it does, what it returns, and what it does not do. Combined with annotations that already cover the safety profile, an agent has enough to call it correctly. Only the shape of the returned instructions is left unspecified.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so the baseline is 4 and there is nothing for the description to disambiguate. No parameter meaning is added or needed.

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 states the verb and resource ('Grade assessment in the user's own LearnWorlds account') and then immediately clarifies the actual deliverable: a step-by-step guide of screens, buttons and fields. That correction is what lets an agent distinguish this from the cotlet_browser_* siblings it must call afterwards. It is not explicitly contrasted with the other learnworlds_* siblings, which keeps it short of a 5.

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 gives a clear two-step workflow: call this tool to get the instructions, then perform the action with cotlet_browser_* in the LearnWorlds Cloud Browser. It also explains why the official REST API is not the route (Learning Center plan requirement plus custom code), which implicitly justifies using this tool. No explicit 'when not to use' statement is provided.

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

All LearnWorlds MCP Server and API by Cotlet toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources