Skip to main content
Glama

Stadika: study abroad and Russian universities

search_ru_universities

Read-only

Ищет вузы России по городу, направлению или профессии и сумме баллов ЕГЭ. Возвращает средний балл ЕГЭ зачисленных на бюджет по направлениям с годом приёма, число зачисленных на бюджет, стоимость с годом, общежитие и ссылку на страницу вуза на uni.stadika.ru.

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

Input Schema

NameRequiredDescriptionDefault
qNoЧасть названия вуза
cityNoГород: Казань, Москва, Санкт-Петербург или слаг kazan
dormNoТолько вузы с общежитием
typeNoГосударственный или негосударственный
limitNoСколько результатов вернуть, до 10
budgetNoТолько направления, где был приём на бюджет
regionNoРегион России: Республика Татарстан, Московская область или слаг respublika-tatarstan (необязательно)
ege_sumNoСумма баллов ЕГЭ абитуриента по трём предметам, например 240
directionNoНаправление: профессия (программист, юрист, психолог, врач, учитель, экономист, дизайнер), слово из названия специальности или код вида 09.03.01
price_maxNoНаибольшая стоимость обучения в год, рубли

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations only declare readOnlyHint and openWorldHint=false; the description goes beyond them by enumerating exactly what comes back (average admitted EGE score with admission year, budget admit counts, tuition with year, dormitory, deep link). It does not disclose default result count, empty-result behavior, or sorting.

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?

Two sentences, front-loaded with the searchable dimensions, then the return payload. Dense but each clause carries information; the return list is long but justified given there is no output schema.

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?

With ten optional parameters and no output schema, the description correctly compensates by spelling out the returned fields, which is the main completeness risk here. Missing only secondary details: default limit, behavior with zero filters, and result ordering.

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 coverage is 100%, so the schema already documents every parameter including examples and enum values, and the baseline of 3 applies. The description only echoes city/direction/ege_sum without adding semantics such as how ege_sum is compared (threshold vs exact) or whether budget/dorm act as hard filters.

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?

States a specific verb and resource ("Ищет вузы России") plus the three search axes (city, direction/profession, EGE sum), which is far more than a restated name. It does not explicitly contrast itself with the sibling get_ru_university, so the search-vs-fetch distinction is only implied by the verb.

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: use this when you want to discover universities matching filters, and get_ru_university presumably when you already know the institution. No explicit when-to-use/when-not-to-use statement, no note that all ten filters are optional or how filters combine (AND vs OR).

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