Skip to main content
Glama
paulsham

Wiki Analytics Specification MCP Server

by paulsham

get_property_details

Retrieve property definitions and identify usage across events and property groups in analytics specifications.

Instructions

Get property definition and see where it is used across events and property groups.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
property_nameYesName of the property to retrieve

Implementation Reference

  • The main handler function for the 'get_property_details' tool. It retrieves the property from propertiesMap, checks if it exists, and computes its usage in property groups and events (direct and via groups).
    handler: async (args) => {
      const prop = propertiesMap.get(args.property_name);
      if (!prop) {
        throw new NotFoundError('Property', args.property_name);
      }
    
      // Find usage in property groups
      const usedInGroups = propertyGroups
        .filter(g => splitMultiLine(g.properties).includes(args.property_name))
        .map(g => g.group_name);
    
      // Find usage in events (direct additional properties)
      const usedInEvents = events
        .filter(e => splitMultiLine(e.additional_properties).includes(args.property_name))
        .map(e => e.event_name);
    
      // Find events that use this property via groups
      const eventsViaGroups = events
        .filter(e => {
          const eventGroups = splitMultiLine(e.property_groups);
          return eventGroups.some(groupName => usedInGroups.includes(groupName));
        })
        .map(e => e.event_name);
    
      return {
        name: prop.property_name,
        type: prop.type,
        constraints: prop.constraints || null,
        description: prop.description,
        usage: prop.usage || null,
        used_in_groups: usedInGroups,
        used_in_events_directly: usedInEvents,
        used_in_events_via_groups: eventsViaGroups
      };
    }
  • Input schema for the 'get_property_details' tool, requiring a 'property_name' string.
    inputSchema: {
      type: 'object',
      properties: {
        property_name: {
          type: 'string',
          description: 'Name of the property to retrieve'
        }
      },
      required: ['property_name']
    },
  • Registration of the 'get_property_details' tool within the exported 'tools' object, including description, input schema, and handler reference.
    get_property_details: {
      description: 'Get property definition and see where it is used across events and property groups.',
      inputSchema: {
        type: 'object',
        properties: {
          property_name: {
            type: 'string',
            description: 'Name of the property to retrieve'
          }
        },
        required: ['property_name']
      },
      handler: async (args) => {
        const prop = propertiesMap.get(args.property_name);
        if (!prop) {
          throw new NotFoundError('Property', args.property_name);
        }
    
        // Find usage in property groups
        const usedInGroups = propertyGroups
          .filter(g => splitMultiLine(g.properties).includes(args.property_name))
          .map(g => g.group_name);
    
        // Find usage in events (direct additional properties)
        const usedInEvents = events
          .filter(e => splitMultiLine(e.additional_properties).includes(args.property_name))
          .map(e => e.event_name);
    
        // Find events that use this property via groups
        const eventsViaGroups = events
          .filter(e => {
            const eventGroups = splitMultiLine(e.property_groups);
            return eventGroups.some(groupName => usedInGroups.includes(groupName));
          })
          .map(e => e.event_name);
    
        return {
          name: prop.property_name,
          type: prop.type,
          constraints: prop.constraints || null,
          description: prop.description,
          usage: prop.usage || null,
          used_in_groups: usedInGroups,
          used_in_events_directly: usedInEvents,
          used_in_events_via_groups: eventsViaGroups
        };
      }
    },
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 describes a read operation ('Get'), implying it's likely non-destructive, but doesn't specify permissions, rate limits, error conditions, or response format. For a tool with zero annotation coverage, this leaves significant gaps in understanding its behavior.

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, efficient sentence that front-loads the core purpose ('Get property definition') and adds useful context ('see where it is used across events and property groups'). There is no wasted language, and it's appropriately sized for the tool's complexity.

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

Completeness3/5

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

Given the tool's moderate complexity (single parameter, no output schema, no annotations), the description is minimally adequate. It explains what the tool does but lacks details on behavioral traits, usage context, or output. Without annotations or an output schema, the agent has incomplete information about how to interpret results or handle errors.

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 'property_name' documented as 'Name of the property to retrieve'. The description adds no additional meaning beyond this, such as format examples or constraints. With high schema coverage, the baseline score of 3 is appropriate, as 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 ('Get') and resource ('property definition'), and specifies what information is retrieved ('see where it is used across events and property groups'). However, it doesn't explicitly differentiate this tool from its sibling tools like 'get_event_implementation' or 'search_events', which might also involve property-related queries.

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. It doesn't mention any prerequisites, exclusions, or specific contexts for usage, nor does it reference sibling tools. The agent must infer usage based solely on the purpose statement.

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