daycare_capacity
Get current capacity by age band for the daycare(s) this org owns.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| daycare_id | No |
Lodi Kids Activities
TDQS
B3.2/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must disclose behavioral traits. It states the operation is a read of current capacity, but does not mention authentication requirements, rate limits, or behavior when the optional parameter is omitted. The return format is not described, leaving gaps for an AI agent.
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 a single, 12-word sentence that is efficient and front-loaded. However, it may be overly terse, missing details that could enhance clarity without significant bloat.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness2/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's simplicity (one optional param, no output schema), the description is incomplete. It fails to clarify the behavior when 'daycare_id' is omitted, the structure of the response (e.g., array of age bands), or any limitations. An agent may require additional assumptions.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters2/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema has one optional parameter 'daycare_id' with no description (0% coverage). The tool description adds 'by age band' context but does not explain the parameter's semantics, such as whether omitting it returns all daycares or the expected format. The added value is minimal.
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 the verb 'Get', the resource 'current capacity', and the scope 'by age band for the daycare(s) this org owns'. It effectively distinguishes from sibling tools like 'daycare_set_capacity' and other admin queries.
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 usage for querying capacity of owned daycares but provides no explicit guidance on when to use this tool versus alternatives like 'daycare_set_capacity' or other admin tools. No exclusions or prerequisites are mentioned.
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.
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.