Skip to main content
Glama

Письмо внутренней почты SmartLMS

lms_get_message
Read-onlyIdempotent

Fetch complete SmartLMS message details by ID: body text, course, sender, recipients, and attachments. Use after listing messages to read full content.

Instructions

Полный текст письма внутренней почты SmartLMS по id (см. lms_list_messages): текст, курс, отправитель, получатели, вложения (имя файла, размер, ссылка на скачивание).

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": {
      "messageId": "<messageId>"
    },
    "name": "lms_get_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
messageIdYesid письма (из lms_list_messages)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.1.2
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / messageId / maximum
      Added value: +9007199254740991
  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, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds value the annotations do not: it discloses the exact returned fields, including attachment name, size and download link, which matters given there is no output schema. Missing only edge behavior such as what happens for an unknown or inaccessible messageId.

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?

One sentence, no filler, front-loaded with the operation and its identifier source, followed by the return-field enumeration. 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?

For a single-parameter read tool with no output schema, the enumeration of returned fields compensates well for the absent output contract, and annotations cover safety. Only minor gaps remain: no mention of behavior when the id is invalid or the caller lacks access.

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?

There is a single parameter with 100% schema description coverage ('id письма (из lms_list_messages)'), so the description merely repeats the schema wording verbatim. Baseline 3 is correct when the schema already carries the semantics.

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 and resource ('Полный текст письма ... по id') and immediately enumerates the payload (text, course, sender, recipients, attachments). It names the sibling lms_list_messages as the source of the id, so an agent can distinguish fetching one message from listing many 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 '(см. lms_list_messages)' establishes the workflow: list first, then fetch by id, which implicitly rules out using this tool for discovery. It gives clear context but no explicit when-not-to-use or error/precondition guidance.

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