Skip to main content
Glama
Sign In
konbu

konbu

by krtw00
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Hybrid

list_events

Retrieve calendar events sorted by start time. Returns id, title, start and end times, all-day flag, and tags.

Instructions

List calendar events belonging to the user, ordered by start time. Returns id, title, start_at, end_at, all_day flag, and tags for each event. For tasks without a fixed time use list_todos; for free-form notes use list_memos. Example: returns [{"id":"ghi09876-...","title":"Standup","start_at":"2026-05-28T10:00:00+09:00","end_at":"2026-05-28T10:15:00+09:00","all_day":false,"tags":["work"]}, ...]. Workflow: typically followed by get_event(id) for full details or update_event(id, ...) to reschedule. Side effects: read-only.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.3
    • removedInput schema / description
      Removed value: -"イベント一覧"
  2. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Discloses read-only side effect and ordering by start time. With no annotations, the description carries full burden; it provides key behavioral traits but could mention pagination or date range limitations.

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?

Front-loaded with purpose, each sentence adds value (example, workflow, side effects). No wasted words.

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?

For a zero-parameter tool with no output schema, the description covers all needed context: purpose, return fields, example, sibling alternatives, workflow, and side effects.

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?

Input schema has zero parameters, schema description coverage is 100%. Baseline 3 is appropriate; description does not need to add parameter details, but it adds value by listing returned fields.

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 verb 'list', resource 'calendar events', and scope 'belonging to the user, ordered by start time'. Additionally distinguishes from sibling tools list_todos and list_memos, fulfilling a specific verb+resource+scope criterion.

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

Usage Guidelines5/5

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

Explicitly instructs when to use alternatives ('For tasks without a fixed time use list_todos; for free-form notes use list_memos') and describes typical workflow ('typically followed by get_event(id) or update_event(id, ...)').

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