Skip to main content
Glama

Enrichment.Kids Activity Marketplace

by io.github.enrichment-kids
OverviewDiscussionsAdmin

Get provider info

get_provider_info
Read-onlyIdempotent

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).

Input Schema

TableJSON 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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema 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"
-]
  2. First observed

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.

All Enrichment.Kids Activity Marketplace toolsInspect
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