Skip to main content
Glama

mu

by mu.micro
OverviewDiscussionsAdmin

Browse events

events_list
Read-onlyIdempotent

List the caller's upcoming events and reminders, each with its id

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum events, default 20, max 100
offsetNoEvents to skip

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. Changed2 schema fields changed
    • addedInput schema / properties / limit
      Added value: +{
+  "description": "Maximum events, default 20, max 100",
+  "type": "number"
+}
    • addedInput schema / properties / offset
      Added value: +{
+  "description": "Events to skip",
+  "type": "number"
+}
  4. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations declare readOnlyHint and idempotentHint, which cover the main behavioral aspects. The description adds context by specifying 'caller's upcoming' and that results include ids, which is consistent with read-only behavior. No contradictions.

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 concise sentence and the input schema is minimal and well-organized. No unnecessary detail or repetition.

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?

The tool is simple and the description provides sufficient context for a listing operation, including the scope ('caller's upcoming') and that each result carries an id. There is no output schema provided, but the key return detail is mentioned. In the context of sibling event tools, this description is adequate.

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?

Both parameters (limit and offset) have clear descriptions in the schema, including default and max for limit. Schema coverage is complete, so the description doesn't need to add further parameter explanation.

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?

Clearly states the verb 'List' and the resource 'caller's upcoming events and reminders', including the detail that each has an id. This distinguishes it from event mutation tools like events_create, events_delete, events_update, and events_free.

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?

Does not explicitly state when to use this tool versus alternatives such as events_create, events_delete, or events_update. No comparison or conditional guidance is provided, so the agent must infer usage from the name and description.

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

All mu toolsInspect
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.

Resources