Skip to main content
Glama

Stadika: study abroad and Russian universities

get_scholarship

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

Input Schema

NameRequiredDescriptionDefault
idYesid стипендии (stadika.ru/scholarships/view/{id})

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 safety is covered by structured data. The description adds real value beyond that by enumerating the returned content (description, requirements, coverage, amount, deadline, official site), which matters because there is no output schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One short sentence, front-loaded with the core purpose followed by the returned fields; every token carries information and nothing is redundant.

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 simple one-parameter read tool with full schema coverage and annotations, the description supplies the missing piece — the shape of the result — since no output schema exists. Minor gaps remain around error behavior and the relationship to search_scholarships.

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?

With a single parameter at 100% schema coverage, the schema already documents 'id' including the stadika.ru URL pattern. The description adds no further meaning about the id's origin or valid range, so 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?

"Полная карточка стипендии" names a specific verb-like action (fetch the full card) and the resource (scholarship), immediately distinguishing it from search_scholarships by implying a single-record detail lookup. It does not explicitly name the sibling, 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' plus the word 'карточка' signals a detail fetch after an id is known. There is no explicit statement such as 'use after search_scholarships to retrieve details' and no note about what happens with 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