Skip to main content
Glama

Immersive Commons

by com.immersivecommons

Create a hackathon team

ic_hack_team_create

Start a team and become its lead. One team per person — leave your current team first. Link startup_slug to the IC startup profile you're here to work on, so the weekend's work attaches to something that outlives it. Args: { eid?, name, startup_slug?, looking_for? }. Returns: { ok, team }. Required scope: hack:team, and you must be registered on the event.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
eidNo
nameYes
looking_forNoSkills you need, e.g. 'a designer, someone who knows Workers'.
startup_slugNoIC startup profile this team is building on.

TDQS

A4.5/5.0
Behavior5/5

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

Annotations are all false, carrying minimal safety info, so the description carries the full burden. It discloses the lead role, the one-team-per-person rule, the startup_slug linkage, the required scope (hack:team), the need to be registered, and the return format ({ ok, team }). This is substantial behavioral context 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?

Every sentence earns its place: the opening states the action, the second covers a key constraint, the third explains a parameter's purpose, and the final lines list args, returns, and requirements. It is front-loaded and compact with no filler.

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 there is no output schema, the description explicitly states the return shape. It covers purpose, constraints, prerequisites (registration and scope), and parameter linkage. It is complete for a team-creation tool, with the only minor gap being the undefined eid parameter.

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 description adds meaning for startup_slug by saying 'Link startup_slug to the IC startup profile you're here to work on, so the weekend's work attaches to something that outlives it.' However, it omits any elaboration on eid (likely event ID) and name beyond the basic Args list. With schema coverage at 50%, the description should compensate for eid's lack of schema description but does not.

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 'Start a team and become its lead,' a specific verb+resource statement that clearly identifies the action. It distinguishes from sibling tools like ic_hack_team_join, ic_hack_team_leave, and ic_hack_team_list by noting the leadership role.

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 provides clear context: 'One team per person — leave your current team first,' which tells the agent when to avoid calling and implies a prerequisite using the leave tool. It also states registration and scope requirements. However, it does not explicitly name alternative sibling tools (e.g., ic_hack_team_join) for joining an existing team.

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