Skip to main content
Glama

Grades by date

get_grades_window

List grades and formative assessments dated within date_from..date_to, without averages (see get_grades). A point grade's raw is a score on the scale its category names.

Instructions

List grades and formative assessments dated within date_from..date_to, without averages (see get_grades). A point grade's raw is a score on the scale its category names. scope also changes the view this login's Librus session remembers and may not apply to formative rows. A grade whose formative_id equals a formative row's assessment.detail_id is one assessment. grade_id, corrects and corrected_by: see get_grades. behaviour_points: only entries dated in the range.

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": {
      "account_alias": "<account_alias>"
    },
    "name": "get_grades_window"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum items in this page.
scopeNoLibrus view: all, or its week or last_login recent-changes filter; not dates.all
cursorNonext_cursor from the previous page; omit for the first page.
date_toNoLast day, YYYY-MM-DD, inclusive; at most 370 days after the first.
date_fromNoFirst day, YYYY-MM-DD, inclusive.
account_aliasYesLogin alias from list_accounts.

Output Schema

NameRequiredDescriptionDefault
itemsYes
scopeYes
date_toYes
identityYes
date_fromYes
paginationYes
observationYes
behaviour_pointsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv2.8.1
    • addedOutput schema / $defs / BehaviourPointEntryItem
      Added value: +{
      +  "properties": {
      +    "category": {
      +      "type": "string"
      +    },
      +    "day": {
      +      "format": "date",
      +      "type": "string"
      +    },
      +    "detail_id": {
      +      "type": "string"
      +    },
      +    "metadata": {
      +      "items": {
      +        "maxItems": 2,
      +        "minItems": 2,
      +        "prefixItems": [
      +          {
      +            "type": "string"
      +          },
      +          {
      +            "type": "string"
      +          }
      +        ],
      +        "type": "array"
      +      },
      +      "type": "array"
      +    },
      +    "points": {
      +      "type": "integer"
      +    }
      +  },
      +  "required": [
      +    "points",
      +    "detail_id",
      +    "category",
      +    "day",
      +    "metadata"
      +  ],
      +  "type": "object"
      +}
    • addedOutput schema / $defs / BehaviourPointsItem
      Added value: +{
      +  "properties": {
      +    "entries": {
      +      "items": {
      +        "$ref": "#/$defs/BehaviourPointEntryItem"
      +      },
      +      "type": "array"
      +    },
      +    "semester": {
      +      "enum": [
      +        1,
      +        2
      +      ],
      +      "type": "integer"
      +    },
      +    "tally": {
      +      "description": "The number shown, never summed with or checked against the entries.",
      +      "type": "integer"
      +    }
      +  },
      +  "required": [
      +    "semester",
      +    "tally",
      +    "entries"
      +  ],
      +  "type": "object"
      +}
    • removedOutput schema / $defs / FormativeGrade / description
      Removed value: -"One row of the grades page's formative-assessment (\"Oceny kształtujące\")\ntable. \"KARTA SPOSTRZEŻEŃ\" (observation card) appears as a subject value.\nThe same item may also appear in the grid with a matching `formative_id`."
    • changedOutput schema / $defs / Observation / properties / observed_at / pattern
      Previous value: -"^[0-9]{4}-[0-9]{2}-[0-9]{2}T[0-9]{2}:[0-9]{2}:[0-9]{2}(?:\\.[0-9]{1,6})?(?:Z|[+-][0-9]{2}:[0-9]{2})?$"New value: +"^[0-9]{4}-[0-9]{2}-[0-9]{2}T[0-9]{2}:[0-9]{2}:[0-9]{2}(\\.[0-9]{1,6})?(Z|[+-][0-9]{2}:[0-9]{2})?$"
    • addedOutput schema / properties / behaviour_points
      Added value: +{
      +  "default": [],
      +  "items": {
      +    "$ref": "#/$defs/BehaviourPointsItem"
      +  },
      +  "type": "array"
      +}
  2. Changed3 schema fields changedv2.7.0
    • addedOutput schema / $defs / GradeItem / properties / corrected_by
      Added value: +{
      +  "anyOf": [
      +    {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null
      +}
    • addedOutput schema / $defs / GradeItem / properties / corrects
      Added value: +{
      +  "anyOf": [
      +    {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null
      +}
    • addedOutput schema / $defs / GradeItem / properties / grade_id
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null
      +}
  3. Changed6 schema fields changedv2.5.0
    • removedOutput schema / $defs / FormativeItem / additionalProperties
      Removed value: -false
    • removedOutput schema / $defs / GradeItem / additionalProperties
      Removed value: -false
    • changedOutput schema / $defs / GradeItem / properties / record_type / enum
      Previous value: -[
      -  "numeric",
      -  "descriptive"
      -]New value: +[
      +  "numeric",
      +  "point",
      +  "descriptive"
      +]
    • removedOutput schema / $defs / PresentationCursor / additionalProperties
      Removed value: -false
    • removedOutput schema / $defs / WindowPagination / additionalProperties
      Removed value: -false
    • removedOutput schema / additionalProperties
      Removed value: -false
  4. Changed7 schema fields changedv2.3.1
    • addedInput schema / properties / account_alias / description
      Added value: +"Login alias from list_accounts."
    • changedInput schema / properties / account_alias / pattern
      Previous value: -"^(?:[^\\s\\x00-\\x1f\\x7f]|[^\\s\\x00-\\x1f\\x7f](?:[^\\s\\x00-\\x1f\\x7f]| )*[^\\s\\x00-\\x1f\\x7f])$"New value: +"^[^\\s\\x00-\\x1f\\x7f](?: *[^\\s\\x00-\\x1f\\x7f])*$"
    • addedInput schema / properties / cursor / description
      Added value: +"next_cursor from the previous page; omit for the first page."
    • addedInput schema / properties / date_from / description
      Added value: +"First day, YYYY-MM-DD, inclusive."
    • addedInput schema / properties / date_to / description
      Added value: +"Last day, YYYY-MM-DD, inclusive; at most 370 days after the first."
    • addedInput schema / properties / limit / description
      Added value: +"Maximum items in this page."
    • addedInput schema / properties / scope / description
      Added value: +"Librus view: all, or its week or last_login recent-changes filter; not dates."
  5. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Given readOnlyHint=false on a list tool, the description earns credit by explaining why: 'scope also changes the view this login's Librus session remembers,' disclosing a hidden stateful side effect and its unreliable effect on formative rows. It adds no pagination or rate-limit context, though the schema's limit/cursor fields largely cover that.

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 scope is front-loaded in the first clause and every later sentence carries substantive field semantics. The prose is telegraphic and fragmentary in places ('grade_id, corrects and corrected_by: see get_grades'), which costs readability but not correctness.

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 an output schema present, return shape needn't be described, and the description fills the remaining gaps: date-range semantics, session-state side effect, and cross-row linking rules. A reader still needs get_grades to understand grade_id/corrects/corrected_by, but that is a deliberate, signposted deferral.

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?

Schema coverage is already 100%, so the baseline is 3, but the description adds real domain meaning on top: what a point grade's raw means, how formative_id links to assessment.detail_id, and that behaviour_points only returns in-range entries. It leaves grade_id, corrects and corrected_by deferred to get_grades.

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?

States a specific verb (List) plus two resources (grades and formative assessments) constrained by date_from..date_to, and explicitly contrasts with get_grades by noting the absence of averages. An agent can distinguish it from get_grades without opening either schema.

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?

The parenthetical '(see get_grades)' routes the agent to the sibling when averages are wanted, which is a genuine alternative-selection cue. It stops short of stating explicit preconditions or when-not-to-use conditions beyond that single redirect.

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