Skip to main content
Glama

search_events

Read-only

Search calendar events by matching title, location, or notes within an optional date range; without dates, it covers 30 days before and after.

Instructions

Find events whose title, location or notes contain the query (ignores case). Without 'start' and 'end' it looks 30 days back and 30 days ahead. Dates are ISO 8601, for example 2026-11-12 or 2026-11-12T09:30:00+01:00. The range is at most 366 days.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "search_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
endNoEnd of the range. A date-only end includes that whole day.
limitNoMost results to return. Default 50, maximum 500.
queryYesText to look for.
startNoStart of the range. Give both 'start' and 'end', or neither.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint=false, so the safety profile is covered. The description adds behavior that is not in the annotations: case-insensitive matching across three fields, the fallback date window applied when start/end are omitted, and a hard 366-day cap on the range — all directly relevant to how results are produced.

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?

Three short sentences, each carrying unique information: match semantics first, then the default window, then date format and range ceiling. Nothing is repeated from the schema and nothing is padding.

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?

For a four-parameter read-only search with no output schema, the description covers match scope, defaults, format and limits — enough to call it correctly. It does not indicate result shape or ordering, which is a modest gap given no output schema exists to carry that information.

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 would be 3, but the description genuinely adds meaning: it explains the coupling rule (give both start and end, or neither) as a behavioral consequence of omitting both, gives concrete ISO 8601 syntax examples, and states the maximum range span. The remaining param detail, such as limit defaults, lives adequately in the schema.

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 names a specific verb and resource plus the exact fields matched (title, location, notes) and the case-insensitivity rule, so an agent knows precisely what it retrieves. It stops short of naming a sibling such as list_events to contrast with, so it does not fully differentiate itself from non-search listing tools.

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

Usage Guidelines3/5

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

It supplies real operating guidance — the default ±30 day window when no range is given, and the 366-day ceiling on ranges — which tells the agent when the tool is valid. However, it never says when to prefer this over list_events or get_event when a specific event is already known, leaving the alternative routing implicit.

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