Lodi Kids Activities

search_daycares

Search licensed daycares in Lodi, CA. Filter by child age (in MONTHS — daycares think in months for under-5s), program kind (daycare / preschool / after_school), facility setting (in_home / center), or claimed-only (more reliable data). Returns up to 10 daycares with hours + tuition where available. For subsidy / bilingual / curriculum filters, follow up with get_daycare on a slug.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Max daycares to return (1-25). Default 10.
`setting`	No	Filter by facility setting. 'in_home' is a family child care home (smaller, residential). 'center' is a commercial facility.
`age_months`	No	Child age in months. Returns daycares whose licensed age range includes this age. Daycares without ages_min/max populated are kept (we don't know they DON'T serve this age).
`claimed_only`	No	If true, only return daycares whose owner has claimed the listing (more accurate data + reliable contact channel).
`program_kind`	No	Filter by program kind.

TDQS

A4.6/5.0

Behavior4/5

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

With no annotations, the description carries full burden. It discloses that the tool returns up to 10 daycares with hours and tuition where available, and explains how the age filter handles missing data. However, it does not mention authentication requirements, rate limits, or whether it is read-only. This is a minor gap.

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 two sentences, front-loading the core purpose and filters. The second sentence provides crucial follow-up guidance without redundancy. Every word 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?

Given 5 parameters and no output schema, the description explains return details (up to 10 daycares, hours+tuition) and the age filter behavior. It lacks sorting/pagination details, but for a search tool with a default limit, it is reasonably complete. Sibling tools like 'search_programs' are clearly differentiated.

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 description coverage is 100%, so baseline is 3. The description adds value beyond schema by noting that child age is in months ('daycares think in months for under-5s') and that claimed-only provides 'more reliable data'. This extra context improves usability.

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 explicitly states 'Search licensed daycares in Lodi, CA' and lists specific filters. It distinguishes from sibling tool 'get_daycare' by mentioning when to use that instead. The verb 'search' is clear and appropriate.

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?

The description provides explicit guidance on when to use this tool versus alternatives: it mentions that for subsidy/bilingual/curriculum filters, one should follow up with 'get_daycare' on a slug. It also explains that 'claimed-only' yields more reliable data, helping agents decide on that filter.

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

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3.2/5.0

Disambiguation5/5

Tools are clearly grouped by prefix (admin_, daycare_, org_, parent_) and within each group have distinct, non-overlapping purposes. For example, parent_add_kid vs parent_remove_kid are unambiguous.

Naming Consistency5/5

All tools follow a consistent snake_case pattern with role prefix and action_noun structure. Minor exceptions like 'nearby_programs' are standalone and do not disrupt the overall consistency.

Tool Count2/5

With 72 tools, this is far beyond the typical well-scoped range of 3-15. While the tools cover multiple user roles, the count is excessive and likely overwhelming for an agent, falling into the 'too many' category.

Completeness3/5

The tool set covers most core workflows for parents, orgs, and admins, but notable gaps exist: there is no tool to create a program or daycare, and admin tools for approving pending claims or discoveries are missing, leaving dead ends.

Resources

Need Help?