Skip to main content
Glama
pmerlin1

SF Early Learning For All (ELFA) & CareWait MCP Server

by pmerlin1
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

search_sf_childcare

Find licensed San Francisco child care and preschool programs with openings by filtering on age, hours, language, zip code, program type, and financial aid.

Instructions

Search the official San Francisco CareWait database of over 500 licensed early care and preschool programs with real-time filters.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
skipNoPagination offset (default 0)
takeNoNumber of results to return (default 20, max 50)
hoursNoSpecific hours (e.g., daytimeCare, schoolHours, beforeCare, afterCare)
ageYearsNoAge of the child in years (e.g. 2 for 2-year-old)
languageNoLanguage taught or immersion language (e.g. "Spanish", "Mandarin", "Cantonese", "French", "Japanese")
scheduleNoSchedule preference: partTime or fullTime
zipCodesNoList of San Francisco zip codes to restrict search to
programTypeNoType of program: licensedCenter (preschool center), licensedFamilyChildCare (in-home), or any
financialAidNoFinancial assistance types accepted (e.g., ["halfCreditELFA"], ["freeTuitionELFA"], ["fullCreditELFA"], ["cctr"], ["headStart"], ["csppFullDay"])
openingsOnlyNoIf true, only returns programs that currently have open spots

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations present, the description carries the burden of behavioral context. It adds 'official... database' and 'real-time filters,' which help set expectations about freshness and scope, but it does not disclose output characteristics, pagination, or edge cases like empty results or invalid filter combinations.

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?

A single, front-loaded sentence with no filler. It communicates the resource, scope, and capability efficiently, and every phrase contributes value.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool has 10 optional parameters and no output schema, so the description's scope-setting sentence is helpful but not fully complete. An agent still depends on the parameter descriptions for effective usage and has no guidance about what the result set looks like beyond 'programs.'

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 description does not need to re-explain parameters. It adds only the general 'real-time filters' framing, which aligns with the schema but does not add meaningful detail beyond it.

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 is specific and actionable: it names the exact resource (official San Francisco CareWait database), the resource type (licensed early care and preschool programs), and the operation (search with real-time filters). It also conveys the tool's profile sufficiently to distinguish it from siblings like get_childcare_details and check_elfa_eligibility.

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?

The description implies a general search-and-filter use case but does not explicitly state when to use this tool versus alternatives such as get_childcare_details or get_smart_recommendations. It gives clear context about what it searches but no exclusion criteria or sibling routing.

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