Wiki Analytics Specification MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_event_implementationB | Get complete event specification with all properties expanded. Use when implementing tracking code. |
| validate_event_payloadB | Validate a tracking implementation payload against the event spec. Returns errors, warnings, and valid fields. |
| search_eventsC | Search for events by name, description, table, or property usage. |
| get_property_detailsB | Get property definition and see where it is used across events and property groups. |
| get_related_eventsC | Find events in the same table/flow as a given event. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| All Analytics Specs | Complete analytics specification with all events, properties, and property groups |
| user_registration_started | User began the registration process |
| user_registration_completed | User completed the registration process |
| email_verified | User verified their email address |
| onboarding_started | User began the onboarding process |
| onboarding_step_completed | User completed an onboarding step |
| onboarding_completed | User finished the entire onboarding flow |
| project_created | User created a new project |
| collaborator_invited | User invited a collaborator to a project |
| file_uploaded | User uploaded a file to a project |
| user_context | Common user identification properties used across most events |
| device_info | Information about the device and platform |
| session_context | Session-level tracking information |
| page_context | Information about the current page |
| user_id | Unique identifier for the user. Generated at registration and immutable. |
| User's email address. | |
| account_created_at | Timestamp when the user account was created. |
| user_tier | Current subscription tier of the user. |
| registration_method | Method used to register an account. |
| referral_code | Six-character alphanumeric referral code. |
| account_type | Type of account created. |
| verification_method | How the user verified their email. |
| time_to_verify | Seconds between registration and email verification. |
| device_type | Type of device being used. |
| platform | Platform or operating system. |
| os_version | Operating system version string. |
| app_version | Application version in semver format. |
| session_id | Unique identifier for the user session. |
| session_start_time | Timestamp when the session began. |
| session_count | Total number of sessions for this user. |
| page_url | Full URL of the current page. |
| page_title | Title of the current page. |
| referrer | URL of the referring page. |
| onboarding_version | Version identifier for the onboarding flow. |
| step_name | Name of the onboarding step completed. |
| step_number | Numeric position of the step in the flow. |
| skipped | Whether the user skipped this step. |
| completion_time | Seconds spent on this step. |
| total_steps | Total number of steps in the onboarding flow. |
| completed_steps | Number of steps the user completed. |
| project_id | Unique identifier for the project. |
| project_name | Name of the project. |
| project_template | Template used to create the project. |
| invitee_email | Email address of the invited collaborator. |
| permission_level | Permission level granted to the collaborator. |
| file_type | MIME type or extension of the uploaded file. |
| file_size_bytes | Size of the uploaded file in bytes. |
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose with no overlap: get_event_implementation retrieves full event specs, get_property_details focuses on property definitions, get_related_events finds contextual events, search_events performs searches, and validate_event_payload validates payloads. The descriptions explicitly state when to use each tool, eliminating ambiguity.
All tool names follow a consistent verb_noun pattern with snake_case (e.g., get_event_implementation, search_events, validate_event_payload). The verbs are descriptive and aligned with the actions (get, search, validate), making the set predictable and readable.
With 5 tools, this server is well-scoped for wiki analytics specification management. Each tool serves a specific role in event and property handling, from retrieval to validation, without being overly sparse or bloated. The count aligns perfectly with the domain's needs.
The tool set covers core workflows comprehensively: retrieving event specs, property details, related events, searching, and payload validation. A minor gap exists in update or creation tools for modifying specifications, but agents can work around this for read-only and validation tasks in the analytics domain.