ClusterHack

List teams

team_list

Read-only

List teams — scoped to what the signed-in account can see: teams they belong to, created, or administer via being an admin of the team's event. This is never a full public directory of every team on the platform.

Filter by event_slug to see just one event's teams, or search to match team/project name and description. Use team_get for the full detail of one team once you have its id.

Input Schema

TableJSON Schema

Name	Required	Description
`page`	No	Page number, starting at 1.
`search`	No	Match against team name, description or project name.
`page_size`	No	Rows per page (max 100).
`event_slug`	No	Only teams at this event.

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already carry readOnlyHint=true and destructiveHint=false. The description adds valuable behavioral context beyond those: the visibility scope is account-dependent, it is never a public directory, and it supports filtering. This meaningfully clarifies what the result set will contain.

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?

Three short sentences: core scope first, then filtering options, then the routing to team_get. Every sentence contributes distinct information with no repetition or 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?

The tool is a simple list operation with four well-documented optional parameters, annotations clarifying read-only and non-destructive behavior, and a description covering scope, filtering, and alternative selection. Nothing critical is missing for an agent to call it correctly.

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?

All four parameters have schema descriptions, giving 100% coverage, so the baseline is 3. The description reinforces event_slug and search usage but does not substantially add meaning beyond the schema's own parameter documentation.

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?

States a specific verb and resource ('List teams') and immediately scopes it to what the signed-in account can see, explicitly ruling out a full public directory. It also distinguishes itself from team_get by pointing to that sibling for single-team detail.

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?

Gives concrete direction on when to filter with event_slug or search, and explicitly routes the agent to team_get for full detail once an id is known. This tells the agent how to select and use the tool, even without opening the schema.

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

All ClusterHack tools Inspect

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.6/5.0

Disambiguation4/5

Tools are grouped by domain prefix and mostly target a distinct resource, but there are several near-overlapping read clusters — notably whoami/event_roles/event_my_membership (all answer 'what roles at event X'), submission_get/submission_page, team_open_roles/team_seeking_members, and company_employees/company_roster. The descriptions do an exceptional job of steering ('use this, not that'), so misselection is unlikely, but the sheer number of such pairs keeps this from a 5.

Naming Consistency4/5

The dominant domain_prefix + noun/verb pattern (event_, team_, submission_, company_, article_) is consistent and readable. Deviations: list_api_endpoints/list_capabilities invert the word order (verb-first) versus event_list/submission_list elsewhere, search and whoami carry no domain prefix, account_how_to_sign_in is a phrase, and read verbs vary between get/list/browse/page/preview.

Tool Count2/5

60 tools is far beyond the 25+ threshold, and the surface is purely read-only — the breadth comes from extremely granular views (22 event_* tools) and many singleton catalogs (event_cities, event_types, event_background_images, article_languages, tag_list, tech_list, company_vacancies) plus six meta/informational tools. The domain is genuinely broad and every tool is distinct, so it reads as heavy rather than chaotic, but the count is still excessive.

Completeness2/5

The set contains zero write tools — no create, update, or delete anywhere — yet the descriptions repeatedly direct callers to absent tools: event_create, event_set_branding, event_add_sponsor, event_submit_registration_answers, invite_join, team_post, team_assign_role, team_remove_member, company_fire_employee, account_export_data, and more. An agent following the descriptions will call nonexistent tools and fail. The read/browse coverage is very thorough, but the complete absence of the write side (which the descriptions themselves treat as existing) is a significant gap.

Resources

Need Help?