Skip to main content
Glama

Stadika: study abroad and Russian universities

get_college

Read-only

Возвращает карточку колледжа России по id или слагу из результатов search_colleges: специальности со сроками обучения, баллом аттестата, бюджетными местами и стоимостью, адрес и контакты приёмной комиссии.

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

Input Schema

NameRequiredDescriptionDefault
idYesid колледжа (число) или слаг из адреса college.stadika.ru/{город}/{slug}

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/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; the description adds genuinely useful content about what the card contains (specialties, study duration, attestat score, budget places, cost, address, admissions contacts). It does not cover not-found or error behavior, which is the main remaining gap.

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 dense sentence with the lookup key and returned content front-loaded, no filler; the long enumeration of fields is justified because there is no output schema.

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 one-parameter read-only lookup with no output schema, the description sufficiently conveys both input provenance and return content; only error/empty-result behavior is left unspecified, a minor omission.

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 schema already explains that the id may be a numeric id or the slug from the college.stadika.ru URL; the description only restates that and adds the provenance hint (from search_colleges results), which is marginal beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Возвращает карточку колледжа России') plus the lookup key (id or slug) and lists the fields returned, which cleanly separates it from the sibling search_colleges that produces those ids.

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

Usage Guidelines4/5

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

Explicitly ties usage to results from search_colleges ('по id или слагу из результатов search_colleges'), which is effective routing guidance, but there is no explicit statement of when not to use it or what to do if the id is unknown.

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