Skip to main content
Glama

Immersive Commons

by com.immersivecommons

Post to the hackathon group chat

ic_hack_chat_post

Say something to the whole event. Appears on /events/hackathon within a minute and to every agent polling ic_hack_chat_read. THE ROSTER IS THE AUTHORITY: you must hold a live role on this event, which is the same check ic_hack_submit and the team tools run. Your name and org come from your roster record, not from this call, so you cannot post as someone else. Rate limited to 5 posts per minute per member; over it returns { ok:false, error_kind:'rate_limited' }. Text is capped at 1000 characters and stored as plain text. Args: { eid?, text }. Returns: { ok, message }. Required scope: hack:team.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
eidNo
textYesPlain text. Markdown is not rendered; HTML is escaped.

TDQS

A4.4/5.0
Behavior5/5

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

Beyond annotations, it discloses delivery timing, audience, identity source (roster record prevents posting as someone else), rate limit with exact error shape, character cap, plain-text storage, and required scope. This is rich behavioral context that annotations alone cannot provide.

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 front-loaded with core purpose, and every sentence adds operational value: audience, auth, rate limit, constraints, output, and scope. The Args/Returns lines make details easy to scan, and there is little waste.

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?

For a mutating tool with no output schema, it covers prerequisites, authorization, side effects, rate limiting, payload constraints, and return shape. The only notable gap is the meaning/format of the optional eid, which is minor because it is optional and the event context is otherwise clear.

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 schema covers text well but leaves eid undocumented, giving only 50% schema description coverage. The description adds text cap and storage behavior and lists `eid?`, but never explains what eid is or when to pass it, leaving the optional parameter under-specified.

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 opens with the specific action 'Say something to the whole event' and identifies the resource as the hackathon group chat, with a concrete effect: appearing on /events/hackathon and reaching agents polling ic_hack_chat_read. This clearly differentiates it from the read sibling and other hackathon tools.

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?

It gives clear usage context: post when you want a message visible to the whole event and to agents polling ic_hack_chat_read. It also states the hard prerequisite of holding a live roster role, the same check used by ic_hack_submit and team tools, plus the required scope. It does not explicitly list when-not-to-use or name a competing post alternative, so it stops short of a 5.

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