Skip to main content
Glama

История заявок в ЕЛК

elk_list_requests
Read-onlyIdempotent

Lists your submitted ELK requests with number, service, status, dates, executor, and form link so you can check certificates, scholarships, or military registration without opening the web portal.

Instructions

Список всех поданных пользователем заявок в ЕЛК (lk.hse.ru/claim): номер, содержание, сервис, статус (например «Выполнено», «На проверке»), даты создания/обновления, исполнитель и ссылка на форму заявки (если есть). Полезно проверить статус ранее поданных обращений (справки, стипендии, воинский учёт и т.п.) без захода в веб-интерфейс.

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_list_requests"
  }
}

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

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds useful behavioral context by stating that the tool returns all user-submitted requests and enumerating the returned fields, including status examples such as 'Выполнено' and 'На проверке'.

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?

The description is front-loaded with the tool's purpose, followed by the returned fields and a practical usage note. It is appropriately sized, with every sentence adding useful information about scope, output, or application.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only list tool with no output schema, the description explains both the scope of the operation and the fields returned. The only parameter is fully covered by the schema, and annotations cover the safety profile, so an agent has enough information to invoke this tool correctly.

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 `limit` is already documented with a default and maximum. The description does not mention `limit` or add any additional meaning beyond what the schema provides, so the baseline score of 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?

The description states a specific verb and resource: it lists all requests submitted by the user in ELK, with an explicit domain hint (lk.hse.ru/claim). It also names the returned fields (number, content, service, status, dates, assignee, link), making the operation unambiguous compared with sibling tools such as notifications, services, or user info.

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 description gives a clear use case: checking the status of previously submitted inquiries (certificates, scholarships, military registration) without using the web interface. It does not explicitly name alternatives or when-not-to-use conditions, but the context is sufficiently clear for an agent to select this tool for request history.

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