Skip to main content
Glama
Sign In
Ninova MCP

Ninova MCP

by hikmedit
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Course Registration Status

obs_get_registration_status

Check if course registration is currently open for the current semester. Get a clear yes/no answer to know when you can register.

Instructions

Return whether course registration is currently open for the student, per semester.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.2.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are provided, so the description carries the behavioral disclosure burden. 'Return' and 'currently open' make this read like a safe, read-only status query, but it does not mention authentication expectations, what 'open' means, or any freshness/term caveats. For a zero-parameter getter, this is adequate but not richly transparent.

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 a single front-loaded sentence with no filler or repetition. Every word contributes meaning: what is returned, for whom, and at what granularity.

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 an output schema available, the description does not need to explain return values or argument formatting. It is mostly complete for a simple status query, though a brief note about required student authentication would strengthen it.

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 has zero parameters and the schema coverage is 100%, so there is no parameter ambiguity to resolve. The description therefore does not need to add parameter-level detail; the baseline of 4 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?

The description uses a clear verb-resource pair ('Return whether course registration is currently open') and adds scope with 'for the student, per semester.' It is unambiguous about the tool's function, but it does not explicitly differentiate itself from similar siblings like obs_public_registration_term or obs_get_registration_options.

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 guidance on when to use this tool versus alternatives. Sibling tools such as obs_public_registration_term and obs_get_registration_options cover related territory, and the description does not state prerequisites, exclusions, or the condition that should lead an agent to pick this tool.

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