UAAR University MCP Server

list_upcoming_events

Read-onlyIdempotent

Retrieve upcoming university events and workshops from UAAR University MCP Server to stay informed about campus activities.

Instructions

List upcoming university events and workshops.

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

Input Schema

Name	Required	Description	Default
`limit`	No
`offset`	No

Output Schema

Name	Required	Description	Default
`count`	Yes
`items`	Yes
`total`	Yes
`offset`	Yes
`has_more`	Yes
`next_offset`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Jan 27, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Annotations already cover key behavioral traits (read-only, non-destructive, idempotent, closed-world), but the description adds useful context by specifying 'upcoming' events and workshops, which clarifies temporal scope beyond what annotations provide. No contradictions with annotations exist.

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, efficient sentence with no wasted words. It's front-loaded with the core purpose, making it easy to parse quickly without unnecessary elaboration.

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 low complexity (simple list operation), rich annotations covering safety and behavior, and the presence of an output schema (which handles return values), the description is reasonably complete. It could improve by addressing sibling differentiation, but overall it provides adequate context for the agent.

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 description coverage is 0%, but the description doesn't mention parameters at all. The schema fully documents 'limit' and 'offset' with defaults and types, so the baseline is 3 as the schema handles parameter documentation adequately without description input.

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 the verb ('List') and resource ('upcoming university events and workshops'), providing a specific purpose. However, it doesn't distinguish this tool from potential siblings like 'admin_add_event' or 'get_latest_news' that might also handle events, missing full differentiation.

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 description provides no guidance on when to use this tool versus alternatives. With siblings like 'admin_add_event' and 'get_latest_news' present, there's no indication of context, prerequisites, or exclusions for selecting 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