Skip to main content
Glama

Уведомления ЕЛК

elk_get_notifications
Read-onlyIdempotent

Retrieves HSE ELK notifications with title, text, date, importance, and read status, letting you review recent account alerts and updates with an optional result limit.

Instructions

Уведомления ЕЛК (колокольчик в шапке, lk.hse.ru/notification): заголовок, текст, дата, важность, прочитано ли.

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

Input Schema

NameRequiredDescriptionDefault
limitNoМаксимум уведомлений

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.2
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observedv0.1.1

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnly/idempotent/non-destructive/openWorld, so the safety profile is covered. The description adds real value by listing the fields the caller will get back (no output schema exists) and identifying the backing source. It does not disclose ordering, truncation behavior, or whether the 100-item cap silently drops results.

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?

A single compact sentence with zero filler; the resource identity and its UI location are front-loaded. It is terse to the point of being slightly telegraphic (the field list reads as a fragment), but nothing is wasted.

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 simple one-parameter read tool with full annotations and no output schema, the description is adequate: it tells the agent what the tool returns and where the data lives. It is incomplete on the operational details an agent would want — result ordering, and whether 'limit' truncates the newest notifications.

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?

Only one optional parameter and schema coverage is 100%, so the schema already documents 'limit' (max 100, default 20). The description adds nothing about what the limit counts against or what happens when it is exceeded, so baseline 3 is appropriate.

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?

Names a specific resource (ELK notifications) and pins it to a concrete surface ('колокольчик в шапке, lk.hse.ru/notification'), which unambiguously separates it from LMS-message siblings such as lms_list_messages. It also enumerates the returned content (title, text, date, importance, read status). It stops just short of a 5 because the verb is implicit — the phrasing is a noun list rather than 'retrieves/lists'.

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 statement of when to use this instead of the many sibling listing tools (lms_list_messages, lms_list_assignments, my_today). The UI location helps an agent recognize the concept but gives no exclusion or selection rule.

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