MyIIS MCP Server

Overview Schema Source Related Servers Discussions Admin

lms_get_resource

Read-only

Download a Moodle learning file and retrieve its metadata by validating the URL against a host whitelist and using an authorized session.

Instructions

Безопасно скачать и получить метаданные учебного файла/документа из СЭО Moodle.

Проверяет URL по белому списку хостов (SSRF protection) и скачивает файл через авторизованную сессию.

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": {
      "url": "<url>"
    },
    "name": "lms_get_resource"
  }
}

Input Schema

Name	Required	Description	Default
`url`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 2, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false, and destructiveHint=false. The description adds meaningful behavior beyond annotations: it says URLs are checked against a host whitelist for SSRF protection and that the file is downloaded through an authorized session, implying authentication requirements. It still omits rate limits or response handling, but the security context is useful.

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 concise sentences, front-loaded with the core action and the safety mechanism. There is no redundant or filler phrasing.

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, the description covers purpose, safety, and authenticated-session behavior. However, with no output schema, it does not describe what is returned (file content versus metadata shape), and the url parameter remains under-specified.

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 clarify the single url parameter. It adds a constraint by stating that the URL is checked against a host whitelist, but it does not specify URL format, accepted schemes, or how to obtain the resource URL, leaving clear 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?

States a specific pair of verbs (download and retrieve metadata) and a specific resource (educational file/document from the Moodle LMS). An agent can distinguish it from sibling tools like lms_get_course or lms_get_page because this tool targets a downloadable file/document resource.

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?

The description implies usage for Moodle file/document resources, but it does not explicitly say when to use this tool instead of siblings such as lms_get_page or lms_get_course. No prerequisites or exclusions are stated, so usage is only implied.

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