Skip to main content
Glama

Stadika: study abroad and Russian universities

search_colleges

Read-only

Ищет колледжи и техникумы России по городу, специальности, поступлению после 9 или 11 класса, общежитию, бюджетным местам и стоимости. Возвращает специальности со сроком обучения, баллом аттестата и ссылку на страницу колледжа на college.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_colleges"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoЧасть названия колледжа
cityNoГород: Екатеринбург, Москва или слаг ekaterinburg
dormNoТолько колледжи с общежитием
typeNoГосударственный или частный
limitNoСколько результатов вернуть, до 10
budgetNoТолько специальности с бюджетными местами
price_maxNoНаибольшая стоимость обучения в год, рубли
specialtyNoСлово из названия специальности (дизайн, программирование, сестринское дело) или код вида 09.02.07
after_gradeNoПоступление после 9 или после 11 класса

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

The annotations already establish readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description goes further and discloses what a result contains (specialties with study duration, attestation score, and a link to the college page on college.stadika.ru), which the annotations do not convey and there is no output schema to carry it. It stops short of describing result ordering or behavior when no filters are supplied.

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?

Two sentences with no filler; the searchable facets come first and the return-value sentence follows. Every clause carries information an agent can act on.

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 nine-parameter tool with full schema coverage, safety annotations, and no output schema, the description covers purpose, filters, and return shape adequately. The remaining gap is minor: nothing about ordering or what happens when zero filters are passed.

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 100%, so every one of the nine parameters is already documented, including the enum options and the city-slug format. The description restates the same facets (city, specialty, after_grade, dorm, budget, cost) without adding format rules, defaults, or interaction behavior. Baseline 3 applies when the schema does the heavy lifting.

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 ('Ищет колледжи и техникумы России') and enumerates the facets it searches on, which makes it readily separable from a university or program search. It never explicitly contrasts itself with the sibling tools 'search_ru_universities' or 'search_programs', so the differentiation is implied by the entity type rather than stated.

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?

The list of supported filters implies the situations where the tool applies, but there is no explicit statement of when to use this versus 'search_ru_universities' or 'search_programs', nor any preconditions. Usage is inferable but not guided.

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