Skip to main content
Glama

Сводка на неделю

my_week
Read-onlyIdempotent

Build a 7-day study plan from classes, SmartLMS/ELK deadlines, exams, and overdue assignments; returns JSON items sorted by urgency with per-source status.

Instructions

План на ближайшие 7 дней (сегодня + 6): расписание занятий, дедлайны SmartLMS и ЕЛК, экзамены/зачёты, просроченные несданные работы. Без почты и уведомлений — для них my_today. Возвращает JSON: items — единый список элементов (kind, when, title, course, place, overdue, unread, source, ...), отсортированный: просроченные несданные первыми, затем по времени, затем без даты; sources — статус каждого источника (ok/error/skipped, текст ошибки, warnings). Если источник недоступен (например, ЕЛК не ответил), сводка всё равно возвращается — смотрите sources.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
itemsYes
windowYes
sourcesYes
generatedAtYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.1.2
    • addedOutput schema / properties / items / items / properties / raw / propertyNames
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / sources / propertyNames
      Added value: +{
      +  "type": "string"
      +}
  2. First observedv0.1.1

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing partial-failure semantics: if a source like ЕЛК fails, the summary is still returned and callers must inspect sources (ok/error/skipped, error text, warnings). Annotations already cover safety (readOnly, idempotent, non-destructive) and openWorldHint fits an aggregator hitting external systems, so this added degradation contract is the high-value content.

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?

Front-loads scope and horizon, then exclusion, then return shape — a sensible order with no filler sentences. It is somewhat dense, and enumerating item fields (kind, when, title, course, ...) duplicates the existing output schema, which is the only real redundancy.

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 zero-parameter aggregator, the definition covers scope, exclusions, error tolerance, and result ordering. An output schema exists, so the description need not detail return values further, yet it still flags the degraded-mode behavior that no schema field alone would convey.

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?

The tool takes no parameters, so there is nothing parameter-wise to disambiguate; baseline 4 applies. The description instead spends its space on the output contract, which is appropriate here.

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?

Names the concrete resource and horizon ("План на ближайшие 7 дней (сегодня + 6)") and enumerates the exact content classes it aggregates: расписание, дедлайны SmartLMS и ЕЛК, экзамены/зачёты, просроченные работы. It also explicitly excludes mail/notifications and points at the sibling my_today, so it is distinguishable without opening schemas.

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 an explicit exclusion with a named alternative: "Без почты и уведомлений — для них my_today", which is a clear routing rule. It does not address overlap with the other close sibling, my_deadlines, which also appears to surface deadline data, so the when-to-use picture is clear but not fully complete.

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