Skip to main content
Glama

Stadika: study abroad and Russian universities

search_programs

Read-only

Поиск программ обучения за рубежом в каталоге Стадики (как на stadika.ru/programs). Возвращает программы с вузом, страной, уровнем, языком, длительностью, стоимостью и дедлайном, а также facets: допустимые значения фильтров.

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

Input Schema

NameRequiredDescriptionDefault
qNoТекст запроса: название программы, вуза или специальности, например «computer science» или «дизайн»
uniNoВуз, слаг адреса stadika.ru/uni/{slug}
cityNoГород: название или слаг (Берлин, milan)
freeNoТолько бесплатное обучение
langNoЯзык обучения: английский (english), немецкий (german), французский (french) ...
pageNoНомер страницы, с 1
sortNo
levelNoУровень: бакалавриат (bachelor), магистратура (master), аспирантура (phd), MBA (mba), короткие курсы (non-degree), postdoc, diploma, certificate
limitNoСколько результатов вернуть: по умолчанию 10, до 20 без ключа и до 50 с ключом (устаревший синоним per_page)
priceNoСтоимость обучения в долларах США в год, диапазон min-max: 0-5000, 10000-
formatNoФормат обучения: очная (full-time), заочная (part-time), вечерняя (evening) ...
onlineNoТолько онлайн
countryNoСтрана: название по-русски или по-английски, слаг или код ISO, несколько через запятую: Германия, Italy, czech-republic, US
deadlineNoДедлайн подачи: в ближайшие 30 дней, в этом месяце, в этом сезоне
durationNoДлительность в месяцах, диапазон min-max: 12-24
per_pageNoРазмер страницы: по умолчанию 10, до 20 без ключа и до 50 с ключом
disciplineNoНаправление: название или слаг (психология, computer-science, business; см. facets.discipline)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds value by disclosing the response shape (program fields plus facets of allowed filter values), but it omits the API-key-dependent result cap and pagination behavior that the schema only hints at.

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 action and scope, then the return contract. No filler; the only mild redundancy is the site-path analogy, which does serve as a concrete mental model.

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

Completeness3/5

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

For a 17-parameter search tool with no output schema, the description does well to name the returned fields and facets. However, it says nothing about result limits, key requirements, or how the many filters combine, which an agent needs to call it correctly at scale.

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 94%, so the schema already documents nearly every parameter with examples and formats. The description's only added semantic is the existence of a facets object that enumerates valid filter values, which is genuinely useful but does not deepen any individual parameter's meaning.

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 ("Поиск программ обучения за рубежом в каталоге Стадики") and enumerates the returned fields (university, country, level, language, duration, cost, deadline) plus facets. It does not differentiate itself from siblings such as search_colleges or search_scholarships, so an agent must infer the boundary from the name alone.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use or when-not-to-use guidance and no mention of alternatives like get_program for detail lookups or the other search_* tools. The reference to stadika.ru/programs implies a catalog-browsing context but leaves the agent to guess routing.

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