Skip to main content
Glama

Stadika: study abroad and Russian universities

get_consultation

Read-only

Как получить помощь с поступлением: ссылка на бесплатную консультацию с наставником Стадики и услуги наставников с ценами в рублях.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

NameRequiredDescriptionDefault
topicNoО чём вопрос (необязательно): страна, программа, стипендия

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/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 and locality profile is covered. The description adds useful content context by saying the response is a consultation link plus ruble-denominated prices, but says nothing about whether the link is static, whether costs are current, or any auth/precondition requirements.

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 compact sentence that front-loads what the tool yields. Every clause carries information (link, free consultation, mentor services, ruble prices). The interrogative framing is slightly awkward for a tool description but wastes no space.

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 single-optional-parameter read-only resource tool with no output schema, the definition covers what is returned (consultation link and prices) well enough to call correctly. The missing piece is guidance on when an agent should surface it versus answering from the catalog tools.

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 single 'topic' parameter is documented in the schema as optional (country, program, scholarship). The description never mentions the parameter, so it adds no meaning beyond the schema; 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 states a specific resource: a link to a free mentor consultation plus mentor service pricing in rubles. That clearly separates it from the sibling lookup tools (get_university, search_programs, etc.), which return catalog data rather than a contact/pricing resource. It is phrased as a question ('Как получить помощь...') rather than a verb+resource action, which costs it the top score.

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: an agent can infer this is the tool to call when a user asks how to get admission help or what mentor services cost. There is no explicit when-to-use, when-not-to-use, or named alternative, and no statement about whether it should be offered proactively vs. only on request.

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