Skip to main content
Glama

Оценки по курсу

lms_get_grades
Read-onlyIdempotent

Fetches a student's SmartLMS course grades by course ID, returning ordered gradebook rows with item names, category hierarchy, and grade values.

Instructions

Оценки студента по курсу SmartLMS (отчёт по пользователю): items — строки журнала по порядку, у каждой name (название элемента или категории), level (уровень вложенности), path (категории-предки), isCategory и grade (текст оценки; null у категории, «-» если оценки ещё нет). Если вёрстка журнала курса не распознана — ошибка.

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

Input Schema

NameRequiredDescriptionDefault
courseIdYesid курса на edu.hse.ru

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.1.2
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / courseId / maximum
      Added value: +9007199254740991
  2. First observedv0.1.1

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), so the description adds real value beyond them: the shape of the returned items, the meaning of null vs "-" in grade, and an explicit failure mode when the course journal layout is unrecognized. Only pagination/ordering guarantees across calls remain unstated.

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?

Front-loaded with the purpose, then the return contract, then the error case — a logical order with no filler. It is a single dense run-on sentence, and splitting the item-field list would improve scanability, but nothing is wasted.

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?

With no output schema, the description carries the burden of explaining returns and does so thoroughly, including field-by-field semantics and the error condition. It stops short of saying how to obtain courseId or whether the report is scoped to the authenticated user, which would complete it.

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 100% — courseId is already documented as the course id on edu.hse.ru with a positivity constraint — so the baseline is a 3. The description adds no further semantics about the parameter, such as whether it is a course id versus a journal id.

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+resource: grades of a student for a SmartLMS course, plus explicitly the per-user report scope. It does not contrast itself with siblings such as lms_list_courses or lms_list_assignments, but the purpose itself is unambiguous.

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 guidance: no statement that courseId comes from lms_list_courses, no note on when to prefer this versus other LMS tools, and no prerequisites or exclusions. The agent must infer usage purely from the name and the single required parameter.

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