Skip to main content
Glama

Stadika: study abroad and Russian universities

search_scholarships

Read-only

Поиск стипендий и грантов на обучение за рубежом (как на stadika.ru/scholarships): сумма, покрытие, уровень, страна, дедлайн.

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

Input Schema

NameRequiredDescriptionDefault
qNoТекст запроса: название стипендии, фонда или вуза
rfNoТолько открытые для граждан России
pageNoНомер страницы, с 1
sortNo
levelNoУровень: бакалавриат (bachelor), магистратура (master), аспирантура (phd), постдок (postdoc), MBA (mba)
limitNoСколько результатов вернуть: по умолчанию 10, до 20 без ключа и до 50 с ключом (устаревший синоним per_page)
womenNoТолько для женщин
amountNoСумма стипендии, диапазон min-max
countryNoСтрана: название по-русски или по-английски, слаг или код ISO: Германия, united-states, CN
coverageNoПокрытие: полное, частичное, только обучение
deadlineNo
per_pageNoРазмер страницы: по умолчанию 10, до 20 без ключа и до 50 с ключом
disciplineNoНаправление: business, management, economics, law, social-sciences, humanities, art, engineering-technology, natural-sciences, life-sciences-medicine-health, environmental-sciences, applied-sciences-professions-arts, sport

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?

The annotations already declare readOnlyHint=true and openWorldHint=false, so safety and data locality are covered without description help. The description adds the useful provenance hint ('как на stadika.ru/scholarships') and the returned attribute set (amount, coverage, level, country, deadline), but says nothing about pagination behavior or the API-key gate on result limits, which only appears buried in the schema.

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?

A single front-loaded sentence with the core purpose first and the facet list after, no filler. The parenthetical site reference is slightly odd but does convey the data model cheaply.

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 13-parameter read-only search with no output schema and rich per-parameter schema descriptions, the description covers purpose and the main result dimensions adequately. The remaining gap is how results are shaped and paginated, plus the key-gated limit behavior, but annotations and schema pick up most of that slack.

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 85%, so the schema already carries most parameter meaning, and baseline is 3. The description's list of facets (сумма, покрытие, уровень, страна, дедлайн) loosely maps to five of the thirteen parameters but adds no format or range detail beyond what the schema states.

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 gives a specific verb+resource ('Поиск стипендий и грантов на обучение за рубежом') and enumerates the searchable facets, so the agent immediately knows this is a filtered search over scholarship/grants for study abroad. It does not contrast itself with siblings like get_scholarship, match_profile or upcoming_deadlines, so differentiation is left to 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 explicit when-to-use guidance: nothing says to use this for discovery vs. get_scholarship for a single record, or why one would prefer upcoming_deadlines or match_profile. Usage is only implied by the enumerated filter facets.

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