Skip to main content
Glama

Junely — Colorado Kids’ Camps & After-School

Search kids’ camps & after-school programs

search_programs
Read-only

Search Junely’s catalog of kids’ summer camps and after-school programs (coverage today: Colorado and Texas), checked against each provider’s own page. Filter by child age, month, region, category, price, and open availability. Freshness is per row, not daily: every result starts from its captured extraction date (can be weeks old); live_verified additionally means Junely re-checked that program’s own page today for after-school listings, or confirmed plausible status/dates at last capture for camp listings — it is not proof every listing was checked today.

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_programs"
  }
}

Input Schema

NameRequiredDescriptionDefault
ageNoChild’s age in years
limitNoMax results (default 10)
monthNoMonth the program should run, e.g. "July" or "7"
queryNoFree-text interest, e.g. "robotics", "horseback riding", "Russian language"
regionNoRegion or city where Junely has listings (today: Colorado and Texas), e.g. "Denver", "Boulder", "Colorado Springs", "Dallas", "Houston", "Austin", "San Antonio"
categoryNoCategory, e.g. STEM, Sports, Arts, Outdoors, Academic
verticalNoCamps (default) or after-school programs
max_priceNoMaximum price in USD
open_onlyNoOnly programs currently open for registration (default false)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / region / description
      Previous value: -"Region or city where Junely has listings (today: Colorado), e.g. \"Denver\", \"Boulder\", \"Colorado Springs\""New value: +"Region or city where Junely has listings (today: Colorado and Texas), e.g. \"Denver\", \"Boulder\", \"Colorado Springs\", \"Dallas\", \"Houston\", \"Austin\", \"San Antonio\""
  2. Changed1 schema field changed
    • changedInput schema / properties / region / description
      Previous value: -"Colorado region or city, e.g. \"Denver\", \"Boulder\", \"Colorado Springs\""New value: +"Region or city where Junely has listings (today: Colorado), e.g. \"Denver\", \"Boulder\", \"Colorado Springs\""
  3. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations only declare readOnlyHint and openWorldHint, so the freshness disclosure is genuinely additive: data starts from a per-row capture date that can be weeks old, and live_verified is carefully scoped as a re-check rather than a guarantee. That is exactly the kind of caveat annotations cannot carry. It stops short of describing result ordering, pagination behavior, or zero-result behavior.

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?

Front-loaded with purpose and scope, then filters, then the freshness caveat. The final sentence about live_verified is dense and slightly convoluted with its camps/after-school branch, but every clause conveys real information.

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?

For a nine-parameter, no-required-arg search tool with no output schema, the definition covers scope, filter affordances, and the interpretation of result freshness. What it lacks is any hint of result shape (fields returned) or behavior when filters are over-narrow, which matters given there is no output schema to fall back on.

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 all nine parameters are already documented with examples and defaults. The description's sentence 'Filter by child age, month, region, category, price, and open availability' largely restates the schema without adding syntax, interaction, or precedence rules (e.g., how query combines with category).

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Search Junely's catalog of kids' summer camps and after-school programs') plus geographic scope (Colorado and Texas). It doesn't name a sibling to contrast with, so differentiation from get_program_details or whats_open is left to inference.

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?

Usage is implied through the filter list (age, month, region, category, price, availability), which tells an agent this is the discovery tool. There is no explicit statement of when to prefer get_program_details, watch_program, or whats_open instead, and no stated prerequisites.

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