Skip to main content
Glama

Stadika: study abroad and Russian universities

search_internships

Read-only

Поиск стажировок за рубежом (как на stadika.ru/internships): страна, город, отрасль, стоимость программы от (USD), оплачиваемые.

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": "search_internships"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoТекст запроса
cityNoГород: название или слаг
pageNoНомер страницы, с 1
paidNoТолько с зарплатой
sortNo
limitNo
priceNoСтоимость программы в USD
countryNoСтрана: название, слаг или код ISO (см. facets.country)
industryNoОтрасль: название или слаг (см. facets.industry)
per_pageNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/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 scope profile is covered. The description adds only that results mirror the stadika.ru/internships catalog and are limited to programs abroad; it says nothing about pagination behavior, result ordering, or the fact that limit/per_page are capped at 10.

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 with the resource first and the filter list after; no filler. It is telegraphic rather than prose, but every phrase carries information about what can be filtered.

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

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 10 parameters, no required params, and no output schema, the description should at minimum explain paging (page plus the redundant limit and per_page) and the shape of results. It covers only the filter vocabulary and leaves an agent guessing how to paginate or what a result entry contains.

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 70%, so most parameters are already documented and the baseline is 3. The description adds a little meaning by framing price as "стоимость программы от (USD)" (a lower-bound cost filter), but it omits q, page, sort, limit and per_page entirely, leaving the duplicate limit/per_page pair unexplained.

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+resource ("Поиск стажировок за рубежом") and enumerates the filter dimensions, so an agent can distinguish it from search_colleges/search_programs/search_scholarships by resource alone. It does not explicitly name or contrast a sibling, which keeps it from 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 through the listed filter facets (country, city, industry, price, paid); there is no explicit statement of when to choose this tool over the other search_* tools, and no mention of prerequisites or result expectations. An agent can infer intent from the resource name, but nothing is spelled out.

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