Skip to main content
Glama

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

lms_open_page
Read-onlyIdempotent

Open any edu.hse.ru page by relative path under an authorized session and return its visible text and links for tasks not covered by existing tools.

Instructions

Открыть любую страницу edu.hse.ru по относительному пути (например /calendar/view.php) под авторизованной сессией и вернуть видимый текст и ссылки. Полезно для сценариев, не покрытых готовыми тулами.

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

Input Schema

NameRequiredDescriptionDefault
pathYesОтносительный путь на edu.hse.ru, напр. /calendar/view.php?view=month

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.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds value annotations cannot: the request runs under an authenticated session and returns visible page text plus links. It omits failure behavior (redirects to login page, invalid path), which keeps it from a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, no filler: the action and scope come first, the return value second, and the positioning clause last. Every clause earns its place.

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 one required parameter, full schema coverage, no output schema, and safety covered by annotations, the description supplies the missing return-value context. Only edge-case behavior (unauthenticated redirects, non-200 paths) is left implicit, a minor gap for a generic page-fetch tool.

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% and the single parameter is already documented with an example in the schema itself. The description repeats 'относительный путь' and an example path, adding no syntax or format detail beyond structured data; baseline 3 applies.

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 (открыть), resource (любая страница edu.hse.ru), access context (под авторизованной сессией) and output (видимый текст и ссылки). The final clause carves out its niche versus the specialized siblings, so an agent can tell it is the generic escape hatch rather than a substitute for lms_get_grades or lms_get_course_materials.

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?

"Полезно для сценариев, не покрытых готовыми тулами" gives explicit fallback guidance: use this when no purpose-built tool exists. It stops short of naming a concrete alternative or warning about when not to use it (e.g. don't scrape grades this way), so it is clear context rather than full routing logic.

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