Skip to main content
Glama

Открыть произвольную страницу ЕЛК

elk_open_page
Read-onlyIdempotent

Open any lk.hse.ru page by relative path using an authorized SSO session, then retrieve its visible text and link list for navigation or data extraction.

Instructions

Открыть любую страницу lk.hse.ru по относительному пути под авторизованной SSO-сессией и вернуть видимый текст и список ссылок на странице. Известные разделы (разведаны 2026-09-15): /task (задачи), /claim (заявления/обращения), /service (сервисы), /student-services (Центр сервиса «Студент» — заказ справок, изменение персональных данных, финансовые вопросы; разделы через ?section=documents&subsection=certificates и т.п.), /faq. Хелпдеск-тикеты создаются на отдельном домене pmo.hse.ru/servicedesk/customer/portal/81/create/ (ссылки на конкретные формы есть на странице профиля и student-services).

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": {
      "path": "<path>"
    },
    "name": "elk_open_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesОтносительный путь на lk.hse.ru, напр. /claim или /student-services?section=documents

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

A4/5.0
Behavior4/5

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

Annotations already declare readOnly/openWorld/idempotent/non-destructive, so the bar is lower, yet the description adds real context: requests run under an authorized SSO session and the result is page-visible text plus links. It also discloses an important boundary — ticket creation happens on a different domain — which prevents a futile call. It stops short of describing auth-failure behavior or dynamic-content rendering limits.

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 action and return values are front-loaded in the first sentence, with the domain caveat placed last. The long parenthetical enumerating student-services subsections is dense but earns its space as routing knowledge; it is the only slightly bloated element.

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 correctly compensates by stating what comes back (visible text and links). Combined with the route catalog and the cross-domain caveat, an agent has enough to call this correctly; only failure modes and content-size expectations are absent.

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 100% and the single parameter is already documented, so baseline would be 3. The description adds value by supplying concrete path examples (/claim, /student-services?section=documents&subsection=certificates) and enumerating valid route families, which makes the relative-path format unambiguous beyond the schema's single example.

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 names a specific verb+resource ('Открыть любую страницу lk.hse.ru по относительному пути') and even states the return shape (visible text plus a list of links), so an agent knows exactly what the call produces. It does not explicitly contrast itself with the sibling elk_get_section or lms_open_page, so differentiation is only implied by the 'any arbitrary page by path' framing.

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 catalog of known sections (/task, /claim, /service, /student-services with query examples, /faq) tells the agent concretely when this tool is the right reach, and the note that helpdesk forms live on a separate domain pmo.hse.ru effectively says when NOT to use it. What is missing is an explicit rule such as 'prefer elk_get_section for structured section data'.

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