Skip to main content
Glama

Immersive Commons

by com.immersivecommons

Update your team's recruiting sign

ic_hack_team_update
Idempotent

Turn your team's recruiting flag on or off and edit what you are looking for. Lead-only, and only for the team you are on: the team id is read from your own membership, so this can never touch another team. Set recruiting: false once you are full, so ic_hack_team_list stops advertising you to people looking for a team. Pass looking_for: "" to clear the text. Works in any phase, including after submissions lock. Args: { eid?, recruiting?, looking_for? } (at least one of recruiting / looking_for). Returns: { ok, team }. Required scope: hack:team, and you must be the team lead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
eidNo
recruitingNofalse once the team is full; true to advertise again.
looking_forNoSkills you still need. Empty string clears it.

TDQS

A4.3/5.0
Behavior4/5

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

Annotations declare readOnlyHint=false (mutation), idempotentHint=true, destructiveHint=false. The description adds useful behavioral context: the team id is derived from the user's membership, so it cannot affect other teams, and it explicitly states required scope and leader permission. It does not contradict annotations and adds value beyond them.

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?

The description is informative but efficiently structured: it opens with the core action, then provides scope, usage examples, argument list, return shape, and permissions. It is slightly long but each sentence adds value without 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?

For a mutation tool with no output schema, the description covers the key aspects an agent needs: what it does, when to use it, scope safety, permissions, return format, and phase-agnostic behavior. The only minor omission is error handling or edge cases, but that is not critical for invocation.

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 covers 67% (descriptions for recruiting and looking_for, none for eid). The description adds contextual meaning: explains when to set recruiting false (when full, to stop advertising) and that looking_for empty clears text. However, eid remains unexplained—its purpose and when it should be provided are unclear, which is a noticeable gap given it appears in the args list.

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 verb and resource: 'Turn your team's recruiting flag on or off and edit what you are looking for.' It distinguishes this from sibling tools like ic_hack_team_create/join/leave by focusing on updating the recruiting sign, and it explicitly scopes to the caller's own team and lead-only access.

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?

Provides explicit guidance: when to set recruiting false (when full) and why (so ic_hack_team_list stops advertising), and how to clear looking_for with an empty string. It also notes the tool works in any phase and is lead-only, giving clear conditions for appropriate use.

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