Skip to main content
Glama

Прогресс потока по ученикам

cohort_progress
Read-onlyIdempotent

По каждому ученику потока: процент курса (считается по обязательным опубликованным урокам, как в кабинете), когда последний раз заходил или проходил урок, сколько дней с тех пор. Плюс доходимость потока: доля тех, кто дошёл до 100 %. Имена — только по ступени 3 (см. описание сервера), иначе «Ученик 14».

Не больше 200 учеников за раз. total, completed и completion_rate считаются по всему потоку, а не по странице; next_offset показывает, с какого места читать дальше, 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": {
      "cohort_id": "<cohort_id>"
    },
    "name": "cohort_progress"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
offsetNo
cohort_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / limit
      Added value: +{
      +  "default": 50,
      +  "title": "Limit",
      +  "type": "integer"
      +}
    • addedInput schema / properties / offset
      Added value: +{
      +  "default": 0,
      +  "title": "Offset",
      +  "type": "integer"
      +}
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already establish a safe, idempotent read, so the description's added value is in the aggregation semantics: totals, completed and completion_rate cover the whole cohort rather than the page, and next_offset returning null marks the end. It also discloses the anonymization rule for names and the 200-student ceiling, though it does not say what happens if limit exceeds that cap or how results are ordered.

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 what is returned, then the completion metric, then the naming caveat, then pagination rules — a logical order with no filler. Slightly dense run-on phrasing, but every sentence carries information.

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 responsibly names the key return fields (total, completed, completion_rate, next_offset) and their scope, which is the main thing an agent needs. It falls short only on the cohort_id meaning and the exact response shape per student.

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%, so the description must carry the parameters, and it only partially does: the 200-per-request ceiling constrains limit, and next_offset explains how to continue from offset, but cohort_id is never described and limit/offset are not named. It compensates enough to call the tool, but leaves real gaps.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific resource and verb: per-student progress within a cohort, with course percentage, last activity date and days elapsed, plus cohort-wide completion rate. It is clearly distinct from list_cohorts or get_course, so an agent can pick it without opening the schema.

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 by the content ('per student of a cohort'), with no explicit statement of when to prefer this over list_cohorts or other progress sources, and no prerequisites or exclusions. The audience and scenario are inferable but not spelled out.

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