Skip to main content
Glama
Sign In
MyIIS MCP Server

MyIIS MCP Server

by OrDinaD
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

iis_get_markbook

Read-only

Retrieve the authorized student's electronic gradebook, including record book number, GPA, and grades by semester and subject for exams, credits, and coursework.

Instructions

Получить электронную зачётную книжку авторизованного студента.

Возвращает: номер зачетки, средний балл, оценки по всем семестрам и предметам (экзамены, зачеты, курсовые).

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The annotations already establish the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=false), so this adds value by describing what is returned (grade book number, GPA, per-semester grades across exams/credits/coursework) — meaningful context given no output schema exists. It stops short of saying whether the result is scoped to the caller only or whether pagination/limits apply.

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?

Two short sentences: the purpose first, the return contents second. No filler, no repetition of the tool name, and it is front-loaded with the core action.

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?

With no parameters and no output schema, the description adequately compensates by enumerating the return payload. The only real gap is the lack of any disambiguation from the very similar iis_get_grade_book sibling.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters (empty schema), so there is nothing to document and the baseline of 4 applies. The description correctly implies no input is required by tying it to the authorized student.

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 ('Получить электронную зачётную книжку') scoped to the authorized student, and enumerates the returned content (record-book number, GPA, grades by semester/subject). However it does not differentiate from the near-duplicate sibling iis_get_grade_book, leaving the agent to guess which of the two to call.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance, no stated prerequisites beyond 'authorized student', and no mention of any alternative — notably it never says how it differs from iis_get_grade_book or iis_get_mark_sheets/iis_get_omissions. The agent gets no routing help.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools