Skip to main content
Glama

Stadika: study abroad and Russian universities

match_profile

Read-only

Rank study programs abroad for a student profile: level, fields, countries, budget, language test scores, GPA. Returns a ranked list with score (0..1), bucket (safe, moderate, ambitious), reasons and gaps with stable codes, «what widens the choice» hints, and a consultation link. Do not send names or contact data.

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": {
      "profile": "<profile>"
    },
    "name": "match_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many programs (default 15)
localeNoLanguage of the texts of reasons and gaps (default ru)
targetNoCatalog: abroad (programs abroad); Russian universities and colleges come later
profileYes

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 only declare readOnlyHint and openWorldHint=false, so the description carries the return-shape burden and does it well: score 0..1, bucket (safe/moderate/ambitious), reasons and gaps with stable codes, 'what widens the choice' hints, and a consultation link. It also adds a privacy constraint not present in annotations. It does not cover result volume or how limit interacts with ranking.

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?

Two sentences, front-loaded with the action and the profile inputs, then the return contract. Dense but every clause carries information; the output enumeration is long but justified given 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 read-only ranking tool with a deeply nested profile and no output schema, the description supplies the return structure, the privacy rule and the catalog scope. Remaining gaps — pagination/limit semantics and what the consultation link points to — are minor for correct invocation.

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 75% and the nested profile is well documented in the schema itself. The description's enumeration of level, fields, countries, budget, language tests and GPA largely restates those schema fields rather than adding format or interaction meaning, and it says nothing about limit, locale or target.

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?

States a specific verb and resource — 'Rank study programs abroad for a student profile' — and enumerates the profile dimensions that drive the ranking. It implicitly separates itself from search_programs by being a ranking rather than a search, but never names a sibling or states the boundary 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 implied: call it when you have a student profile and want ranked matches rather than a raw catalog listing. The one explicit rule is a negative constraint ('Do not send names or contact data'), and the target enum notes Russian universities 'come later', which hints at the sibling search_ru_universities. No explicit when-not or alternative routing is 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