Skip to main content
Glama
Sign In
AlgoChains MCP Server

AlgoChains MCP Server

Official
by AlgoChains
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

track_platform_event

Idempotent

Record platform analytics events, including page views, signups, and purchases, to monitor soft-launch funnels.

Instructions

Track a platform analytics event (page_view, signup, broker_connected, purchase, etc.). Used for soft-launch funnel monitoring.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "event_type": "<event_type>"
    },
    "name": "track_platform_event"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo
deviceNo
user_idNo
referrerNo
event_typeYesEvent type: page_view, signup, email_verified, waitlist_join, broker_connected, bot_started, purchase, conversion
propertiesNo
session_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv22.7.1

TDQS

A3.5/5.0
Behavior2/5

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

Annotations already indicate idempotency and non-destructiveness. Description adds only the soft-launch monitoring context, not expanding on side effects, auth requirements, or rate limits. Limited value beyond 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?

Single sentence, no fluff, directly states purpose and usage context. Efficient and front-loaded.

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?

With 7 parameters, low schema coverage, and no output schema, the description should provide more parameter context or return value details. Only event type examples and use case given, leaving agent with many unknowns.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 14% (only event_type described). Description lists examples but does not explain other parameters like page, device, user_id. Minimal added value.

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 'Track a platform analytics event' with examples like page_view, signup, broker_connected, purchase. It distinguishes this tool from the many getter/setter siblings by specifying its role in soft-launch funnel monitoring.

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?

Explicitly mentions 'used for soft-launch funnel monitoring', providing a clear context of when to use. Does not mention alternatives or exclusions, but the context is sufficient for agent selection among siblings.

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

Deploy Server

Other Tools