Skip to main content
Glama

Stadika: study abroad and Russian universities

upcoming_deadlines

Read-only

Возвращает дедлайны подачи заявок на зарубежные программы и стипендии в окне дат (по умолчанию следующие 90 дней) по стране или региону, уровню и направлению, ближайшие первыми.

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

Input Schema

NameRequiredDescriptionDefault
toNoКонец окна, ГГГГ-ММ-ДД
fromNoНачало окна, ГГГГ-ММ-ДД, по умолчанию сегодня
kindNoПрограммы, стипендии или всё, по умолчанию all
levelNoУровень: бакалавриат (bachelor), магистратура (master), аспирантура (phd)
regionNoРегион мира: Европа, Азия, Ближний Восток, Океания, Африка, Северная Америка, Южная Америка
countryNoСтрана: название по-русски или по-английски, слаг или код ISO: Италия, Germany, IT
disciplineNoНаправление: название или слаг (психология, computer-science)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already establish that this is a read-only, closed-world lookup, so the description's burden is light. It usefully adds two behavioral facts the annotations do not carry - the default 90-day window and the nearest-first ordering - but says nothing about result caps, pagination, or what a deadline record contains.

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?

A single sentence with the resource, the filter dimensions, the default window, and the sort order, all front-loaded. No filler and nothing repeated from the schema verbatim.

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 read-only filtered list with full parameter documentation and no output schema, the description covers what is needed to call it correctly. The remaining gap is volume behavior - how many deadlines come back and whether there is a limit - which matters for a feed-style tool.

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?

Schema coverage is 100%, so the baseline is 3, and the description earns a bump by supplying the default for the `to` bound (next 90 days), which the schema does not state anywhere. It also confirms that country and region are alternative geographic filters and that both programs and scholarships are returned by default.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb and resource: returning application deadlines for foreign programs and scholarships, with filters by country/region, level, and discipline. That makes it distinguishable from detail-fetching siblings like get_program or get_scholarship, though it never names an alternative explicitly.

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?

Usage is implied rather than stated: the 90-day default window and the sort order hint at 'use for an upcoming-deadline overview'. There is no explicit guidance about when to prefer this over search_programs or get_program, nor any note on when-not to use it.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources