Penguin Statistics

List events

list_events

Read-onlyIdempotent

Lists the events (limited-time activities) of a game server: status now (open, upcoming or closed), open and close times, whether a rerun. By default the open and upcoming events with their stage IDs (for get_stage_drops), or the latest 3 if there are none; open_only=false lists every event, latest first, with stage counts only. The main story and the permanent side stories are not events.

Input Schema

Name	Required	Description
`lang`	No	Language of the names in the result: the language the user writes in, zh, en, ja or ko (en for other languages, and if omitted).
`limit`	No	Most events to return, 1 to 50. Default 20.
`server`	Yes	Game server the user plays on: CN (mainland China: 国服, 官服, B服), US (global, English: 国际服, 美服), JP (日服) or KR (韩服). Stages, events and drop rates differ by server. Use the server the user named or the conversation makes clear; a user writing Chinese, Japanese or Korean most likely plays CN, JP or KR. If you can't tell, ask the user which server they play on before calling. Name the server in your answer.
`open_only`	No	true (default): the events open or upcoming on the server, with their stages; if there are none, the latest 3. false: every event of the server, latest first, without their stages.

Output Schema

Name	Required	Description
`now`	Yes	The time of the statuses, RFC 3339 in UTC
`note`	No
`events`	Yes
`server`	Yes
`source`	Yes
`openOnly`	Yes
`truncated`	Yes	Whether limit left out older events

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedOct 23, 2026

removedInput schema / properties / lang / default
```
Removed value: -"en"
```

changedInput schema / properties / lang / description

Previous value: -"Language of the names in the result: zh, en, ja or ko. Default en."New value: +"Language of the names in the result: the language the user writes in, zh, en, ja or ko (en for other languages, and if omitted)."

removedInput schema / properties / server / default
```
Removed value: -"CN"
```

changedInput schema / properties / server / description

Previous value: -"Game server: CN (China), US (global, English), JP (Japan) or KR (Korea). Default CN."New value: +"Game server the user plays on: CN (mainland China: 国服, 官服, B服), US (global, English: 国际服, 美服), JP (日服) or KR (韩服). Stages, events and drop rates differ by server. Use the server the user named or the conversation makes clear; a user writing Chinese, Japanese or Korean most likely plays CN, JP or KR. If you can't tell, ask the user which server they play on before calling. Name the server in your answer."

addedInput schema / required
```
Added value: +[
+  "server"
+]
```

First observedOct 23, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive behavior, so the safety profile is covered. The description adds non-trivial behavioral nuance not in the annotations: the fallback to the latest 3 events when nothing is open, and that stages are included only in the default mode while open_only=false returns counts only.

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?

Three dense sentences that are front-loaded with the core purpose and scope exclusion. Every clause carries information, though the middle sentence packing defaults, fallback, and mode differences together is somewhat heavy to parse.

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

Completeness5/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. Given four parameters with full schema coverage and rich server-selection guidance, the description supplies everything an agent needs: scope, default behavior, mode differences, and the cross-reference to get_stage_drops.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds meaning beyond the schema by linking open_only's two modes to concrete result shapes (stages included vs stage counts only, latest-first ordering) and its automatic fallback behavior. It reinforces the server-selection requirement rather than merely restating the enum.

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?

States a specific verb ('Lists') and resource ('events'), and defines the term parenthetically as 'limited-time activities'. It also carves out scope ('The main story and the permanent side stories are not events') and points to get_stage_drops for the stage-specific follow-up, so an agent can distinguish it from siblings without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explains the default result path (open/upcoming events, or latest 3 if none) and the alternative (open_only=false lists everything, latest first with counts only), plus the negative scope for story content. It lacks explicit guidance on when to prefer this over search_stages, but the routing to get_stage_drops for stage IDs covers the main adjacent need.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Penguin Statistics tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.