Skip to main content
Glama
Sign In
westlake

westlake

by yizhang-dream
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

events_upcoming

Retrieve campus events scheduled within the next N days, including today, so agents can answer what is happening soon at Westlake University.

Instructions

未来 N 天内的活动预告（含今天）。

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

Input Schema

NameRequiredDescriptionDefault
daysNo未来天数窗口，默认 14。

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden, yet it discloses nothing beyond the time window: no ordering, no pagination, no cap on result count, no indication of what an 'event' record contains or whether past events are excluded. Only the 'includes today' boundary is added.

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?

A single short clause with zero filler, and the time window is front-loaded. It is efficient rather than padded, though the brevity edges into under-specification rather than polished conciseness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter, no-required-args read tool with no output schema, a short description can be adequate, and the inclusive-window detail is the key thing an agent needs. Still missing is any hint of what the events are or what comes back, which matters given the crowded calendar/news sibling set.

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 100% and the single `days` parameter already documents its default of 14 and 0–90 bounds. The description adds one genuine clarification the schema lacks — that today counts toward the window — which is meaningful but minimal; baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"活动预告" plus a time window (next N days, including today) identifies the resource and its scope, but no verb is stated and the domain is ambiguous — with siblings like calendar_today, calendar_week, news_latest and career_latest in the list, an agent cannot tell whether these are campus events, calendar entries, or announcements. It is understandable but not sharply differentiated.

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?

No guidance on when to pick this over calendar_today, calendar_week, or news_latest, and no exclusions or prerequisites. The agent must infer usage purely from the name and the day-window phrasing.

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