Skip to main content
Glama
Sign In
itu-mcp

itu-mcp

by yatuk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Portal Notifications

obs_get_notifications
Read-onlyIdempotent

Read İTÜ Portal notifications using your logged-in account to view announcements and updates.

Instructions

Read İTÜ Portal notifications (requires login).

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

Input Schema

NameRequiredDescriptionDefault
limitNo
notification_idNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv1.2.1
    • addedInput schema / properties / limit
      Added value: +{
+  "default": 20,
+  "title": "Limit",
+  "type": "integer"
+}
    • addedInput schema / properties / notification_id
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Notification Id"
+}
    • removedOutput schema / additionalProperties
      Removed value: -true
    • addedOutput schema / properties
      Added value: +{
+  "result": {
+    "additionalProperties": true,
+    "title": "Result",
+    "type": "object"
+  }
+}
    • addedOutput schema / required
      Added value: +[
+  "result"
+]
    • changedOutput schema / title
      Previous value: -"obs_get_notificationsDictOutput"New value: +"obs_get_notificationsOutput"
  2. Addedv0.2.3

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds the login prerequisite, which annotations do not convey, but says nothing about pagination or what limit does at the boundary. With annotations doing the heavy lifting, this is an adequate-but-thin 3.

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

Conciseness4/5

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

One sentence, front-loaded with the action and resource, with the login constraint appended. It wastes no words, though the brevity reflects under-specification rather than disciplined conciseness.

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?

An output schema exists, so return values need not be described, and the login requirement is noted. However, with two undocumented parameters, no enumerated/documented filter behavior, and no channel disambiguation among sibling notification tools, the definition is incomplete for correct invocation.

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

Parameters1/5

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

Schema description coverage is 0% and the description never mentions either parameter. An agent cannot tell from this text that limit caps results at 20 by default or that passing notification_id appears to fetch a single notification rather than list. No compensation for a fully undocumented schema.

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 ('Read İTÜ Portal notifications'), so the agent knows exactly what it fetches. It does not differentiate from near-neighbors like mail_list_inbox, get_itu_announcements, or get_dashboard_announcements, so an agent cannot tell which notification channel this covers.

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?

The only usage signal is the parenthetical '(requires login)'. There is no guidance on when to choose this over the many sibling read/announcement tools, nor when to pass notification_id versus listing.

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