Enrichment.Kids Activity Marketplace

Get activity details

get_activity_details

Read-onlyIdempotent

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.

Input Schema

Name	Required	Description	Default
`slug`	Yes	Activity URL slug returned by search_activities (e.g., 'summer-coding-camp-petaluma').

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 2, 2026
- removedInput schema / additionalProperties
```
Removed value: -false
```

Changed3 schema fields changedMay 14, 2026

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"
+]
```

First observedMar 16, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare read-only, open-world, and idempotent behavior, so the description does not need to restate safety. It adds some useful context by clarifying that share_url points to an external registration and payment page, but it does not describe error behavior, missing-slug handling, or other operational constraints.

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 front-loaded with the core action, then enumerates the returned activity and session fields. The single long sentence is information-dense and mostly earns its place, though it would be easier to scan as separate sentences.

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?

With no output schema, the description does important work explaining the return shape, including session-level fields and the registration link. It is complete enough to invoke correctly, though edge cases such as invalid or unavailable slugs are not covered.

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%, including the required slug and an example. The description only repeats that lookup is by slug and adds no format or constraint beyond what the schema already provides.

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: returns full details for one enrichment activity identified by its slug. It clearly distinguishes a single-activity detail lookup from a list/search operation, though it does not explicitly name the sibling tools to sharpen that contrast.

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: call this when you already have an activity slug and need full details for that activity. The description gives no explicit when-not guidance or alternatives, and the slug provenance appears only in the schema rather than in the description.

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

All Enrichment.Kids Activity Marketplace tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?