Skip to main content
Glama

Stadika: study abroad and Russian universities

get_program

Read-only

Полная карточка программы: описание, требования, стоимость, длительность, дедлайн, ссылки на страницу программы и сайт вуза.

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

Input Schema

NameRequiredDescriptionDefault
idYesid программы (число) или слаг адреса stadika.ru/program/{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. The description adds real value beyond them by spelling out the response contents (a full program card including cost, deadline, and external links), which matters because no output schema exists. It omits error/not-found behavior, which keeps it from a 5.

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 front-loaded sentence naming the resource first, then enumerating returned fields — no filler. The dense field list is efficient rather than padded, though it could have been split to also carry usage guidance.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 full schema coverage, the description is complete: it tells the agent what the record contains, which substitutes for the absent output schema. Nothing needed to invoke it correctly is missing.

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% and the schema already explains that 'id' accepts a numeric program id or a stadika.ru/program/{slug} slug. The description adds no meaning beyond that, so the 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?

The description names a specific verb+resource ('Полная карточка программы') and enumerates the fields returned (description, requirements, cost, duration, deadline, links), so an agent knows exactly what it gets. It does not explicitly contrast itself with the sibling search_programs, so it stops short of a 5.

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: the required 'id' parameter makes clear this is a single-record lookup, presumably after finding an id via search_programs. There is no explicit statement of when to use this versus search_programs, nor any note about what happens for an unknown id.

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