Skip to main content
Glama

Stadika: study abroad and Russian universities

get_ru_university

Read-only

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

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>"
    },
    "name": "get_ru_university"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesid вуза (число) или слаг адреса uni.stadika.ru/{slug}

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 already establish readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds genuine behavioral value by detailing what the card contains, including the non-obvious 'сведения, которых в каталоге нет' (data not present in the catalog), which tells the agent this is a richer source than a plain listing. It stops short of describing not-found behavior or data freshness.

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?

One front-loaded sentence that leads with the verb and resource before listing payload fields; every clause carries information. The trailing enumeration is dense but not padded, though it could be split for readability.

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?

No output schema exists, so the description carries the burden of describing return values, and it does so field by field. For a single-parameter read-only lookup with annotations, the remaining gaps (error/not-found handling, freshness of EGE statistics) are minor.

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?

With a single parameter at 100% schema description coverage, the schema already explains that id accepts a numeric id or the slug from uni.stadika.ru/{slug}. The description restates the same URL template without adding format rules, fallback behavior, or examples, so baseline 3 applies.

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?

Names a specific verb and resource ('Возвращает карточку вуза России') and enumerates the payload (programs with average EGE scores and year, cost, dormitory, admissions contacts, off-catalog data), so the agent knows exactly what it retrieves. It does not differentiate itself from the plausible sibling get_university or from search_ru_universities, leaving that inference to the agent.

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 only implied by the input condition 'по id или слагу' — i.e. call this when you already have a university id or site slug. There is no explicit statement of when to prefer this over get_university or when to start with search_ru_universities instead, and no prerequisites or exclusions are given.

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