Skip to main content
Glama
Sign In
Ninova MCP

Ninova MCP

by hikmedit
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

OBS Authentication Status

obs_auth_status

Check whether your ITU account can sign in to OBS (obs.itu.edu.tr) via girisv3 single sign-on, confirming authentication status before accessing the system.

Instructions

Check whether the ITU account can sign in to OBS (obs.itu.edu.tr) via girisv3 single sign-on.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.2.0

TDQS

A4/5.0
Behavior3/5

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

With no annotations provided, the description carries the full burden. 'Check whether ... can sign in' indicates a read-only status operation and names the SSO mechanism, but it does not disclose whether the check itself requires an existing session or has side effects, such as refreshing a token.

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 redundancy. Every word adds meaning, and the key action ('Check') appears first.

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 zero-parameter status check with an output schema, the description captures the essential behavior. The only gap is that it does not mention prerequisites like an active session or how this relates to refresh_session, but this is a minor omission for such a simple tool.

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, so the schema already covers everything. The description adds useful context about the OBS/girisv3 SSO target, which is sufficient when no parameters exist.

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 uses a specific verb ('Check') and a precise resource ('whether the ITU account can sign in to OBS via girisv3 single sign-on'), which clearly distinguishes it from the generic auth_status sibling. The title and description align and convey exactly what the tool evaluates.

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 implies this is a preflight auth check for OBS operations, but it does not explicitly state when to use it over alternatives like auth_status or obs_refresh_session. No exclusions or when-not-to-use guidance is provided.

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