Skip to main content
Glama

Search Centers Tool

search_centers
Read-onlyIdempotent

Search Kidincare for licensed childcare centers, daycares and preschools in the United States. Filter by keyword, city, state or ZIP code. Returns name, address, phone, ages served and the Kidincare page for each center. Use get_center with a returned id for full details.

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

Input Schema

NameRequiredDescriptionDefault
cityNoCity name, e.g. "Philadelphia".
limitNoHow many centers to return.
queryNoCenter name or program type, e.g. "montessori" or "head start".
stateNoUS state name or two-letter code, e.g. "Pennsylvania" or "PA".
zip_codeNoFive-digit US ZIP code.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so safety is covered. The description adds value by enumerating the return fields (name, address, phone, ages served, Kidincare page link) and by flagging the follow-up tool, though it says nothing about result ordering or 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three dense sentences: purpose and geography first, then filters, then the return payload, then the next-step tool. No filler and no repetition of the tool name.

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

Completeness5/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 compensates by listing the returned fields, and it names the follow-up tool for the deeper record. All five optional filters are accounted for, so an agent can call this correctly without further context.

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%, with each of the five parameters documented with examples and the limit bounded 1-20. The description only restates the filter categories at a high level and adds no syntax or combination guidance beyond the schema, so the baseline 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?

Specific verb (search) plus resource (licensed childcare centers, daycares, preschools), geographic scope (United States), filter dimensions, and the fields returned. It is clearly distinguishable from the sibling get_center, which it names as the detail-lookup path.

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?

Gives clear usage context — search by keyword, city, state or ZIP — and routes the agent to get_center with a returned id when full details are needed. It does not state when this should be chosen over search_guides or list_cities, but that omission is minor for a discovery tool.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources