procare-mcp

Overview Schema Source Related Servers Discussions Admin

list_programs

Retrieve a list of childcare programs such as camps, preschool, after-school, and summer activities. Filter by school or active status to find current offerings.

Instructions

List programs (camps, preschool, after-school, summer).

Use when: "what programs do we currently offer?" or "show me the active summer programs at school 1234."

Args: school_id: restrict to one school. active: filter by active flag (True / False / None = all).

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

Input Schema

Name	Required	Description	Default
`active`	No
`school_id`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 11, 2026

TDQS

A3.8/5.0

Behavior2/5

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

No annotations are provided, so the description carries full burden. It only mentions listing and filtering, but omits behavioral traits such as read-only nature, pagination, limits, or whether it returns all programs matching criteria. This is insufficient for a list tool.

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 extremely concise, using two sentences for purpose and usage, then a clear args list. Every word adds value, no repetition or filler.

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 the tool's simplicity and existence of an output schema, the description covers purpose, usage, and parameter meaning adequately. Missing details like default behavior (returns all programs) are implied but not explicit; still sufficient for a straightforward list 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?

With 0% schema coverage, the description adds basic semantics: 'school_id: restrict to one school' and 'active: filter by active flag (True / False / None = all).' It clarifies the default for active but does not elaborate on the meaning of 'active' in context or other aspects like format.

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 clearly states 'List programs (camps, preschool, after-school, summer)', using a specific verb and resource. It distinguishes from sibling tools like 'get_program' (single vs. list) and other list tools by specifying program types.

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?

The description provides explicit 'Use when' examples covering common queries like 'what programs do we currently offer?' and 'show me the active summer programs at school 1234.' It does not explicitly mention when not to use or alternatives, but the context is clear.

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

Deploy Server