Lodi Kids Activities

search_programs

Search youth programs in the cities Kyds Activities serves (Lodi, Galt, and growing — pass city; defaults to Lodi, CA). Filter by free-text query (program name or description), category (Sports, Music, Arts, Academics, Swimming, etc.), child age (integer in years — programs that accept that age), free-only flag, or season. Returns up to 15 matching programs with full details for decision-making (cost, schedule, location, registration status).

Input Schema

Name	Required	Description
`age`	No	Child age in years. Returns programs whose age range includes this age.
`city`	No	City slug to search in (e.g. 'lodi', 'galt'). Defaults to Lodi. Call list_cities for the current list.
`limit`	No	Max programs to return (1-30). Default 15.
`query`	No	Free-text search across program name + description (case-insensitive substring match).
`season`	No	Filter by season — e.g. 'Summer', 'Fall', 'Spring', 'Winter', 'Year-Round'.
`category`	No	Program category. Common values: Sports, Music, Arts, Academics, Swimming, Gymnastics, Dance, Enrichment, Free Programs.
`free_only`	No	If true, only return programs with $0 cost.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 2, 2026

addedInput schema / properties / city

Added value: +{
+  "description": "City slug to search in (e.g. 'lodi', 'galt'). Defaults to Lodi. Call list_cities for the current list.",
+  "type": "string"
+}

First observedMay 19, 2026

TDQS

A3.5/5.0

Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses the default city, the 15-result cap, and the rich return contents (cost, schedule, location, registration status), but it omits permissions, pagination behavior beyond the cap, and any total-count behavior.

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?

The description is three sentences and front-loads the core scope before filters and return details. It is efficient overall, though the return-details sentence partially repeats the limit behavior already implied by the schema.

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 seven-parameter search tool with no output schema and no annotations, the description covers purpose, defaults, filter dimensions, result cap, and what the returned details include. It gives enough context to call the tool correctly, though it stops short of describing pagination or ordering semantics.

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 description coverage is 100%, so the schema already documents all seven parameters in detail, including defaults and accepted values. The description restates the filter meaning but adds little semantic value beyond what the schema provides.

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 states a specific verb and resource: searching youth programs, with a clear geographic scope (Lodi, Galt, and growing). It clearly separates this from daycare search by naming 'youth programs,' but it does not explicitly contrast with siblings like nearby_programs or get_program.

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?

Usage is implied by the filter list and default city, so an agent can infer this is the tool for broad program searches. However, there is no explicit when-to-use or when-not-to-use guidance versus alternatives like nearby_programs or search_daycares.

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

All Lodi Kids Activities 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?