Skip to main content
Glama

Stadika: study abroad and Russian universities

get_university

Read-only

Возвращает карточку зарубежного вуза по id или слагу адреса stadika.ru/uni/{slug}: страна, город, место в рейтинге THE с годом, число программ и диапазон стоимости по уровням обучения.

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

Input Schema

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

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?

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered and the bar is lower. The description adds genuine behavioral context by spelling out what the returned card contains (ranking position with year, program count, cost ranges), which is the useful extra for a lookup tool.

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?

One front-loaded sentence: verb, resource, keying method, then payload. No filler and no repetition beyond the unavoidable parameter restatement.

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 no output schema, the description compensates by listing exactly which fields come back, which is what an agent needs to reuse the result. Minor gaps remain around not-found/invalid-id behavior, but the essential contract is present.

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% and the single parameter's schema description already states that `id` accepts a numeric id or the {slug} from stadika.ru/uni/{slug}. The description restates this without adding format rules, validation notes, or examples, so it is a baseline 3.

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 states a concrete verb and resource ("Возвращает карточку зарубежного вуза") and enumerates the returned fields (country, city, THE ranking with year, program count, cost range by level). The qualifier "зарубежного" implicitly separates it from the Russian-university siblings, though it never names that counterpart explicitly.

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: fetching a single foreign university by id or slug, with the slug format shown as stadika.ru/uni/{slug}. It never says when to prefer this over search_programs/search_ru_universities or how to obtain a valid id in the first place, so the agent must infer the lookup path.

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