Little Milwaukee

get_events

Read-onlyIdempotent

Returns listed public events in Milwaukee County from the Little Milwaukee events calendar, the same data as https://littlemilwaukee.com/events. Filter by type, cost, neighborhood or suburb, venue, kid friendly, dates and text. Each event has its page URL, start and end, type and cost each with the source that states it, venue, neighborhood, point, organizer, an .ics file and the source that lists it. Check the time with the source before going.

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

Input Schema

Name	Required	Description
`q`	No	Words in the name, venue, organizer or description.
`to`	No	Last date, YYYY-MM-DD. Default 30 days after from; at most 92 days after.
`cost`	No	free, under-10, 10-to-25, over-25 or unknown (no price listed). By the lowest price.
`from`	No	First date, YYYY-MM-DD, Milwaukee time. Default today.
`type`	No	One calendar type.
`limit`	No	How many events, default 50, at most 200.
`venue`	No	A venue key: the place page slug, or the venue name as a slug, as the calendar's venue filter writes it.
`kid_friendly`	No	Only events a source lists for children, and family events.
`neighborhood`	No	A neighborhood or suburb slug, for example bay-view or wauwatosa.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 3, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already establish read-only, idempotent, closed-world behavior, so the description is not carrying the safety burden. It still adds real value beyond them: it discloses the exact return payload (page URL, start/end, type and cost each with a citing source, venue, neighborhood, point, organizer, .ics file) and warns that times should be verified against the source, which signals possible data staleness.

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?

Purpose and scope are front-loaded in the first sentence, followed by filters and then the returned fields. The middle sentence is a long enumeration but each item is informative; the closing caveat is short and earns its place.

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?

With no output schema, the description usefully enumerates return fields, and date-window and limit constraints are covered by the schema, so an agent can call this correctly. Minor gaps remain around result ordering and what happens when filters match nothing, but nothing essential is missing for a read-only listing tool.

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 coverage is 100%, so the schema already documents every filter, its enum values, formats, and defaults. The description restates the filter axes at a high level ('type, cost, neighborhood or suburb, venue, kid friendly, dates and text') without adding syntax or edge-case behavior beyond what the schema provides, so the baseline of 3 applies.

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?

The description opens with a specific verb and resource ('Returns listed public events in Milwaukee County from the Little Milwaukee events calendar') and anchors scope with a concrete reference URL. An agent can tell this apart from write-side siblings such as submit_event or from generic lookups like search or get_place 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?

It gives clear context for when this is the right tool: retrieving calendar events, with the available filter axes enumerated. It does not name alternatives or exclusions (e.g., when to prefer search or get_place instead), so it stops short of explicit routing guidance.

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

All Little Milwaukee 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.

Resources

Need Help?