Skip to main content
Glama

Immersive Commons

by com.immersivecommons

Tail the IC event log (agent subscribe primitive)

ic_events_next
Read-only

Cursor-based read of the calling user's agentic event log. IC publishes events that personal agents subscribe to — tier_requested, tier_approved, tier_denied (more types arrive as append sites land). Pass since = your last-seen event.id (omit for full backlog); response carries cursor (largest id returned), has_more (re-poll immediately if true), and as_of (server time). Optional types[] filter; default returns all entitled types. Events carry actions[] — affordances the agent can render (one-tap reply) or auto-invoke (with policy). Per-user scoped server-side: a token tied to user X only sees X's events. Replay-safe: events are immutable and id-keyed. Args: { since?, types?, limit? }. Returns: { events, cursor, has_more, as_of }. Required scope: none beyond a valid token with a tied Clerk identity.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax events per page. Default 50, max 500.
sinceNoYour last-seen event id. Omit / 0 for full backlog (capped at `limit`).
typesNoOptional event-type filter. Known types: tier_requested, tier_approved, tier_denied, inbox_envelope. Unknown strings are dropped silently.

TDQS

A4.4/5.0
Behavior5/5

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

Discloses read-only nature, per-user scoping, immutability, replay-safety, and required authentication context. Adds significant behavioral context beyond annotations, such as event types and actions array.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single paragraph, front-loaded with purpose, dense with information. No wasted sentences, though could benefit from slight structuring for scanning.

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

Completeness5/5

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

Given no output schema, the description comprehensively explains response fields (cursor, has_more, as_of, events, actions), usage pattern, filtering, scoping, and required scope. Leaves no major gaps for a read 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. Description adds minimal extra meaning for input parameters; the schema already covers details. No additional constraints or nuances beyond what schema provides.

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 the tool is for cursor-based reading of the user's agentic event log, specifying it as an 'agent subscribe primitive'. It distinguishes itself from sibling event tools by focusing on per-user, cursor-based polling.

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?

Provides clear usage instructions: pass 'since' for incremental reads, re-poll on 'has_more', optional types filter. Does not explicitly compare with alternatives like ic_events_get or ic_events_get_live, but the context is self-contained.

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

All Immersive Commons 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

A3.7/5.0
Disambiguation4/5

Most tools are clearly scoped to distinct actions (e.g., ic_hack_apply vs. ic_hack_register, ic_rooms_create vs. ic_rooms_join). A few pairs could confuse an agent: floor10_submit_highlight vs. floorcast_push both submit HighlightStories but to different queues, and ic_directory_search / ic_agent_directory_lookup / ic_admin_list_members overlap in searching members. Overall, the long descriptions help disambiguate, but the volume requires careful reading.

Naming Consistency3/5

The dominant pattern is ic_<domain>_<verb>_<object> (e.g., ic_admin_list_pending_events, ic_headsets_checkout), but there are notable deviations: floor10_* and floorcast_* prefixes break the ic_ convention, and a few tools use noun-style names (ic_health, ic_capabilities, ic_donations_total). Verb placement also varies (get_* vs *_get, e.g., ic_get_my_membership vs. ic_membership_set_profile). Still, most names are readable and predictable.

Tool Count1/5

175 tools is an extreme count for a single MCP server, far beyond the 50+ threshold that indicates an unwieldy surface. While the platform covers many domains (events, files, hackathon, headsets, prints, rooms, etc.), bundling everything into one server makes discovery and selection difficult. This would be better split into several narrowly-scoped servers.

Completeness4/5

The tool set covers nearly every lifecycle for each domain: CRUD for files/folders, full hackathon admissions and judging, headset lending with waivers and incidents, print farm submission and handoffs, and room coordination. Minor gaps exist: no delete for files/folders, no cancel for events, and some actions (like revoking a Z.ai key or tearing down a room) are explicitly left to human console use. Overall, the surface is remarkably comprehensive for the stated scope.

Resources