Skip to main content
Glama
paulsham

Wiki Analytics Specification MCP Server

by paulsham

get_related_events

Find related analytics events in the same table or flow to understand event relationships and dependencies for implementation.

Instructions

Find events in the same table/flow as a given event.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
event_nameYesName of the event to find related events for

Implementation Reference

  • The handler function retrieves the specified event, then filters all events in the same event_table, excluding the input event, and returns their names and descriptions.
    handler: async (args) => {
      const event = eventsMap.get(args.event_name);
      if (!event) {
        throw new NotFoundError('Event', args.event_name);
      }
    
      const relatedEvents = events
        .filter(e => e.event_table === event.event_table && e.event_name !== args.event_name)
        .map(e => ({
          event_name: e.event_name,
          description: e.event_description
        }));
    
      return {
        event: args.event_name,
        table: event.event_table,
        related_events: relatedEvents
      };
    }
  • Input schema defining the required 'event_name' parameter.
    inputSchema: {
      type: 'object',
      properties: {
        event_name: {
          type: 'string',
          description: 'Name of the event to find related events for'
        }
      },
      required: ['event_name']
    },
  • Full tool definition and registration within the exported tools object.
    get_related_events: {
      description: 'Find events in the same table/flow as a given event.',
      inputSchema: {
        type: 'object',
        properties: {
          event_name: {
            type: 'string',
            description: 'Name of the event to find related events for'
          }
        },
        required: ['event_name']
      },
      handler: async (args) => {
        const event = eventsMap.get(args.event_name);
        if (!event) {
          throw new NotFoundError('Event', args.event_name);
        }
    
        const relatedEvents = events
          .filter(e => e.event_table === event.event_table && e.event_name !== args.event_name)
          .map(e => ({
            event_name: e.event_name,
            description: e.event_description
          }));
    
        return {
          event: args.event_name,
          table: event.event_table,
          related_events: relatedEvents
        };
      }
    }
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool finds related events but does not describe how results are returned (e.g., format, pagination), any limitations (e.g., rate limits, access controls), or side effects. This leaves significant gaps in understanding the tool's behavior beyond its basic function.

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, clear sentence that directly states the tool's function without unnecessary words. It is front-loaded and efficient, with every part contributing to understanding the purpose, making it appropriately sized and well-structured.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has no annotations and no output schema, the description is incomplete. It lacks details on return values, behavioral traits, or usage context, which are critical for a tool that likely returns a list of events. The description does not compensate for these gaps, making it insufficient for full understanding.

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 input schema has 100% description coverage, with the single parameter 'event_name' documented as 'Name of the event to find related events for'. The description adds no additional meaning beyond this, such as examples or constraints, so it meets the baseline of 3 where the schema does the heavy lifting.

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?

The description clearly states the tool's purpose with a specific verb ('Find') and resource ('events'), specifying they are related through being in the same table/flow as a given event. However, it does not explicitly differentiate from sibling tools like 'search_events' or 'get_event_implementation', which might also involve event retrieval, leaving room for ambiguity.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives such as 'search_events' or 'get_event_implementation'. It implies usage when needing events related by table/flow, but lacks explicit when/when-not instructions or named alternatives, offering minimal practical direction.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/paulsham/wiki-mcp-analytics-test-1.1.0'

If you have feedback or need assistance with the MCP directory API, please join our Discord server