Skip to main content
Glama

Enrichment.Kids Activity Marketplace

by io.github.enrichment-kids
OverviewDiscussionsAdmin

Server Details

Find kids enrichment activities: camps, classes, after-school programs, and tutoring near you.

If you are the author of this connector, you can claim ownership with GitHub, an HTTP challenge, or a DNS record. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Last Tested
Transport
Streamable HTTP
URL

TDQS

A4.6/5.0

Scored across 3 tools

Disambiguation5/5

Each tool targets a distinct resource and action: search_activities returns listings, get_activity_details provides full session-level details for a specific activity, and get_provider_info focuses on provider profiles. No overlap or ambiguity exists between them.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern in snake_case: search_activities, get_activity_details, get_provider_info. This makes the API predictable and easy to navigate.

Tool Count5/5

With 3 tools, the server is well-scoped for its purpose of discovering and viewing enrichment activities. Each tool has a clear role, and the count falls comfortably within the ideal 3-15 range.

Completeness4/5

The core consumer workflow of searching, viewing details, and checking provider info is fully covered. Registration is intentionally handled externally via share_url, so there are no dead ends. A minor missing feature could be a categories endpoint, but search already accepts category filters.

Available Tools

3 tools
get_activity_detailsGet activity detailsA
Read-onlyIdempotent
Inspect

Returns full details for one enrichment activity identified by its "slug": description, provider organization, location, age range, categories, policies, photos, and its sessions. Each session carries dates, local start and end times with timezone, price and any price tiers, capacity and spots remaining, waitlist availability, drop-in availability, meeting days, and a "share_url" — a link to that session's registration page on enrichment.kids, where registration and payment are completed.

ParametersJSON Schema
NameRequiredDescriptionDefault
slugYesActivity URL slug returned by search_activities (e.g., 'summer-coding-camp-petaluma').

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already establish read-only and idempotent behavior. The description adds substantial behavioral context by enumerating the exact fields returned (description, provider, sessions, prices, capacity, etc.) and disclosing that registration/payment happen externally via the share_url. This goes well beyond what annotations provide.

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 a single, well-structured sentence that leads with the action and resource, then provides a detailed list of return contents. Every listed item adds value and the length is justified by the tool's rich output. No fluff.

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 must explain return values, and it does so comprehensively for both activity-level and session-level details, including the external registration flow. The single parameter is fully documented via the schema, making the description complete for this 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?

The schema covers 100% of parameters and already describes slug as the URL slug returned by search_activities. The description only repeats 'identified by its slug' without adding new meaning. Since schema coverage is high, the baseline of 3 is appropriate.

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 uses a specific verb ('Returns') and resource ('full details for one enrichment activity') with a clear identifier ('slug'). It distinguishes itself from siblings like search_activities (which lists activities) and get_provider_info (which gets provider info) by focusing on detailed per-activity retrieval.

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 implies a workflow: the slug is returned by search_activities, and this tool follows to retrieve full details. This gives clear context for when to use it. However, it doesn't explicitly name alternatives or state when not to use it, so it falls just short of a 5.

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

get_provider_infoGet provider infoA
Read-onlyIdempotent
Inspect

Get profile and active listings for an enrichment activity provider (organization). Pass organization_id from search_activities results, or provider_name to look up by name (optionally narrowed by city/state).

ParametersJSON Schema
NameRequiredDescriptionDefault
cityNoOptional city narrowing for provider_name lookup
stateNoOptional two-letter US state narrowing for provider_name lookup
provider_nameNoProvider name to resolve when organization_id is unavailable
organization_idNoProvider organization ID from search_activities results

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already mark the tool as read-only and idempotent. The description adds behavioral context by specifying what is returned (profile and active listings) and the two lookup paths, without contradicting the annotations.

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?

Two concise, front-loaded sentences convey purpose and usage without any filler or repetition of schema fields.

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?

For a read-only lookup tool with no required parameters and no output schema, the description sufficiently covers what the tool does and how to invoke it. It identifies input provenance and result scope, making it complete for its complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema descriptions already cover 100% of parameters, so the baseline is 3. The description enriches this by explaining the relational source of organization_id and the alternative provider_name lookup with optional narrowing by city and state.

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 tool retrieves profile and active listings for an enrichment activity provider, using specific verbs and resources. It distinguishes itself from siblings like search_activities and get_activity_details by focusing on provider-level data.

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?

It gives explicit lookup guidance: use organization_id from search_activities results, or fall back to provider_name with optional city/state narrowing. It doesn't explicitly contrast with get_activity_details, but the context and sibling names make the intended usage clear.

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

search_activitiesSearch activitiesA
Read-onlyIdempotent
Inspect

Searches children's enrichment activities (camps, classes, after-school programs) in the United States by keyword, city and state or latitude/longitude radius, participant age, session date range, and category. Returns a paginated list of listings; each result carries the activity name, its "slug", the provider organization, location, age range, categories, a price range where available, and a "url" for the listing page. Results are ordered by relevance to the query and are not influenced by paid placement. The "slug" field is the identifier accepted by get_activity_details.

ParametersJSON Schema
NameRequiredDescriptionDefault
cityNoCity name (e.g., 'Petaluma', 'San Francisco')
pageNoPage number (default: 1)
limitNoResults per page (default: 20, max: 50)
queryNoKeyword search (e.g., 'coding camp', 'ballet', 'science')
stateNoTwo-letter US state code (e.g., 'CA', 'OR', 'WA')
age_toNoMaximum participant age (0–19; 19 = adult)
date_toNoLatest session end date (YYYY-MM-DD)
age_fromNoMinimum participant age (0–19; 19 = adult)
latitudeNoLatitude for proximity search
date_fromNoEarliest session start date (YYYY-MM-DD)
longitudeNoLongitude for proximity search
categoriesNoComma-separated category IDs
distance_milesNoSearch radius in miles (default: 25, max: 100)

TDQS

A4.5/5.0
Behavior4/5

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

The annotations already establish read-only, idempotent, and open-world behavior. The description adds meaningful behavioral detail on top: paginated results, relevance-based ordering, independence from paid placement, and the role of slug as the identifier for get_activity_details. It does not mention rate limits, but that is not a significant gap given the existing annotations.

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 sentences, front-loaded with the core action and resource, with no redundant restatement of schema fields. Every sentence contributes: what it searches, what it returns, and how the results relate to a sibling tool.

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?

Despite 13 parameters and no output schema, the description covers the purpose, filter groups, return fields, pagination, ordering, and cross-tool linkage. Combined with the fully-described input schema and safety annotations, this is sufficient for an agent to select and invoke the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3. The description adds relational parameter semantics beyond individual schema entries: it groups location parameters into city/state versus latitude/longitude radius modes, summarizes age and date range filters, and implies pagination via 'paginated list.' This helps an agent compose valid queries more effectively.

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 states a specific verb ('Searches'), a concrete resource ('children's enrichment activities in the United States'), and the key filter dimensions. It clearly distinguishes this list/search tool from the sibling tools by describing the returned listing and the slug handoff to get_activity_details.

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 establishes a clear usage context: searching for activities by keyword, location, age, date, and category. It also points toward get_activity_details for detail lookup via the slug, but it does not explicitly state when not to use search_activities or how it relates to get_provider_info.

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

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 1 tool update
    • Changedsearch_activities4 fields changed
      • changedInput schema / properties / age_from / description
        Previous value: -"Minimum participant age (4–19)"New value: +"Minimum participant age (0–19; 19 = adult)"
      • changedInput schema / properties / age_from / minimum
        Previous value: -4New value: +0
      • changedInput schema / properties / age_to / description
        Previous value: -"Maximum participant age (4–19)"New value: +"Maximum participant age (0–19; 19 = adult)"
      • changedInput schema / properties / age_to / minimum
        Previous value: -4New value: +0
  2. 1 tool update
    • Changedget_provider_info5 fields changed
      • addedInput schema / properties / city
        Added value: +{
+  "description": "Optional city narrowing for provider_name lookup",
+  "minLength": 1,
+  "type": "string"
+}
      • changedInput schema / properties / organization_id / description
        Previous value: -"Provider organization ID"New value: +"Provider organization ID from search_activities results"
      • addedInput schema / properties / provider_name
        Added value: +{
+  "description": "Provider name to resolve when organization_id is unavailable",
+  "minLength": 1,
+  "type": "string"
+}
      • addedInput schema / properties / state
        Added value: +{
+  "description": "Optional two-letter US state narrowing for provider_name lookup",
+  "maxLength": 2,
+  "minLength": 2,
+  "type": "string"
+}
      • removedInput schema / required
        Removed value: -[
-  "organization_id"
-]
  3. 2 tool updates
    • Removedcheck_availability
    • Changedget_activity_details3 fields changed
      • removedInput schema / properties / module_id
        Removed value: -{
-  "description": "Activity ID (numeric). Use slug instead when available — it is more reliable.",
-  "exclusiveMinimum": 0,
-  "type": "integer"
-}
      • changedInput schema / properties / slug / description
        Previous value: -"Activity URL slug (preferred). Use the slug returned by search_activities (e.g., 'summer-coding-camp-petaluma')."New value: +"Activity URL slug returned by search_activities (e.g., 'summer-coding-camp-petaluma')."
      • addedInput schema / required
        Added value: +[
+  "slug"
+]
  4. 4 tool updates
    • First observedcheck_availability
    • First observedget_activity_details
    • First observedget_provider_info
    • First observedsearch_activities

Related MCP Connectors

Related MCP Servers

Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources