Skip to main content
Glama
CipherxHub

vit-bhopal-vtop-mcp-server

by CipherxHub
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

check_pass_eligibility

Read-onlyIdempotent

Determines if you will pass each VIT Bhopal course by applying official CAT, TEE, and 75% attendance rules, and reports the TEE marks you still need.

Instructions

Answer 'will I pass this course?' for every subject, using VIT Bhopal's actual pass rules rather than guessing. ALWAYS quote BOTH scales when asked what to score. Each CAT is a 50-mark paper needing 20, which is worth 6 of the 15 that CAT carries on the 100-point course scale. The TEE (FAT) is a 100-mark paper worth 30 of 100, and must reach 40 - worth 12 of those 30. So the canonical answer is '20/50 in each CAT, worth 6 of 15 each, and 40/100 in the TEE, worth 12 of 30'. Rules applied: passing is 80 raw marks out of 200 (CAT-I 20 + CAT-II 20 + TEE 40), equivalently CAT-I + CAT-II + TEE >= 80 raw. The TEE's own end goal is 40 of 100, and whatever the two CATs fall SHORT of 40 BETWEEN THEM is added to it - this is net, so a CAT above 20 offsets one below it (10 and 10 needs the TEE at 60, but 30 and 10 needs only 40). There is no re-test. Attendance must be >= 75.0% exactly to sit any exam. READ teeRequiredRaw AS THE ANSWER to 'what do I need in the TEE'. Do NOT present totalIfTeeClearedAtMinimum as a requirement - it is an OUTCOME: the course total you would finish with by scoring exactly the TEE minimum, i.e. bankedSoFar + teeRequiredMarks. The attendance marks are excluded from it because they are a projection awarded only after the last instructional day. Working-day and class counts come from the academic calendar and timetable, so holidays and day-order Saturdays are accounted for. If the calendar cannot be read, upcomingClasses is null and calendarAvailable is false with a calendarNote explaining why - that means UNKNOWN, not zero. semesterId is optional; omit for current semester. Requires login.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
refreshNoBypass the short cache and re-read the page from VTOP. Results are cached for 60 seconds so follow-up questions are instant; set this when you specifically want to know whether something has just been updated.
semesterIdNoSemester ID (e.g. 'AP2024251'). If omitted, uses the current/latest semester.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.5

TDQS

A4.2/5.0
Behavior5/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive), and the description adds substantial extra context: a 60-second cache with a bypass flag, a login requirement, an explicit no-retest rule, and a failure mode where an unreadable calendar yields nulls plus calendarAvailable=false rather than zeros. That is well beyond what the annotations convey.

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

Conciseness3/5

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

Purpose is front-loaded in the first sentence, but the body is long and repetitive, re-deriving pass arithmetic (20/50, 6 of 15, 40/100, 12 of 30) and restating the canonical answer. Since the tool computes the result, much of this domain detail and the scripted user-facing phrasing could be trimmed without losing invocation guidance.

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 output schema, the description usefully explains two key output fields and their semantics (teeRequiredRaw as the answer, totalIfTeeClearedAtMinimum as an outcome), plus null-handling. It still omits the overall response shape (per-subject structure, other fields), but is largely complete for a complex domain tool.

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 100%, so both parameters are already documented, and the description's line 'semesterId is optional; omit for current semester' merely repeats the schema. The refresh/cache framing adds a little interpretive value but no syntax or format detail beyond the schema, so the baseline of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and outcome ('Answer "will I pass this course?" for every subject') and anchors the scope to VIT Bhopal pass rules. It is clearly distinguishable from siblings like get_marks, get_internal_totals, and calculate_attendance, which return raw data rather than a pass verdict.

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

Usage Guidelines4/5

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

It gives clear context (answering a pass/fail question with real rules) and even directs the agent to specific output fields for specific user questions ('READ teeRequiredRaw AS THE ANSWER'). It also warns against misusing totalIfTeeClearedAtMinimum. However, it never names an alternative tool or explicitly states when to use a sibling instead.

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