Skip to main content
Glama

convalytics

by io.github.Dan-Cleary

recent_events

Read-onlyIdempotent

Return the most recent custom events for a specific project, optionally filtered to one event name and/or one user. PII (userEmail, userName, props) is redacted by default; pass redact: false to include them.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoOptional event name to filter by (e.g. 'signup_completed'). Omit to return events of any name.
userNoOptional. Filter to one visitor/user. Accepts userEmail (case-insensitive) or visitorId (exact). For the full per-user snapshot prefer user_activity.
limitNoMaximum number of events to return. Default 20, max 100.
redactNoIf true (default), userEmail/userName are null and props is {}. Set to false to include them.
projectYesProject name (case-insensitive, e.g. 'slopbench') or project id from list_projects.

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnly and idempotent. The description adds important behavioral context about PII redaction by default and how to include it, which is beyond annotations and helps the agent understand data sensitivity.

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 sentences with front-loaded main action and options. Every sentence is informative with no fluff.

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

Completeness4/5

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

Covers purpose, filters, redact, and hints at alternatives. Missing output format details, but without an output schema, the description provides sufficient context for this straightforward tool.

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?

Schema coverage is 100%, so baseline is 3. The description restates parameter purposes but does not add significant meaning beyond the schema; it mainly summarizes existing field descriptions.

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 it returns recent custom events for a project with optional filters, and distinguishes from siblings like 'user_activity' and 'events_count'.

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

Usage Guidelines5/5

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

Explicitly describes filtering options, redact behavior, and suggests 'user_activity' for full per-user snapshots, providing clear guidance on when to use this tool versus alternatives.

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

All convalytics toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4/5.0
Disambiguation5/5

All tools have clearly distinct purposes. Funnel operations (compute, create, delete, get, list, update) are well-separated from event tools (events_count, recent_events) and pageview tools (pageviews_count, top_pages, top_referrers). Composite snapshots (user_activity, weekly_digest) and utility tools (get_usage, list_projects) are unique.

Naming Consistency3/5

Naming pattern is inconsistent: some tools use verb_noun (compute_funnel, create_funnel), others noun_verb (events_count, pageviews_count), and some are adjective_noun (recent_events, top_pages) or noun_noun (user_activity, weekly_digest). While readable, the lack of a consistent convention reduces predictability.

Tool Count4/5

15 tools is at the upper boundary of 'well-scoped' but still appropriate for an analytics platform. Each tool serves a necessary function without unnecessary duplication, though a few more could be justified.

Completeness4/5

The tool set covers core analytics operations: CRUD for funnels, event and pageview counting, top pages/referrers, user and weekly snapshots, and project/usage info. Minor gaps exist (e.g., no session-level detail), but overall it addresses common analytics queries well.

Resources