Skip to main content
Glama
Sign In
iitkgp-erp-mcp

iitkgp-erp-mcp

by MSR327
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_grades

Retrieve grades for a specific semester or all semesters. Pass semester name to filter results.

Instructions

Fetch grades. Pass semester like 'Semester 3' to filter, or leave empty for all.

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

Input Schema

NameRequiredDescriptionDefault
semesterNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior2/5

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

With no annotations provided, the description must disclose behavioral traits. It only states 'Fetch grades' and parameter behavior, omitting details like authentication requirements, side effects, or error handling. This is insufficient for a tool with no annotation support.

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?

The description is two sentences with no fluff, front-loading the purpose and immediately following with parameter guidance. Every sentence serves a clear function.

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?

Given the tool's simplicity (one optional parameter, output schema exists), the description covers the essentials. It does not detail the output format, but that is presumably documented in the output schema. The description is adequate for this scope.

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?

Schema description coverage is 0%, so the description must compensate. It explains the parameter 'semester' with a concrete example ('Semester 3') and clarifies that an empty value retrieves all grades, adding meaningful context beyond the schema's type and default.

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 clearly states 'Fetch grades' as the verb+resource, which is specific. However, it does not explicitly differentiate from sibling tools like get_cgpa, get_sgpa, or get_grade_distribution_tool, which also handle grade-related data.

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?

The description provides guidance on when to use the filtering parameter ('Pass semester like 'Semester 3' to filter, or leave empty for all'), but it does not mention when not to use this tool or suggest alternative tools from the sibling list.

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