reject_join_requestReject a pending request to join a community you run. Requires community_id + user_id; you must be its creator or admin.
| Name | Required | Description | Default |
|---|---|---|---|
| user_id | Yes | ||
| community_id | Yes |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate destructiveHint=true and readOnlyHint=false. Description adds role requirement and parameter necessity but does not disclose additional behavioral details like side effects or irreversibility.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Extremely concise: two short sentences with no extraneous information. Front-loaded with action and resource.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Covers basic purpose and preconditions but lacks output/return information, error conditions, and post-action effects. Acceptable for a simple tool but could be more complete.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
With 0% schema coverage, description only mentions required parameter names without explaining their purpose. Agent needs to infer that user_id identifies the requester. Insufficient compensation for missing schema descriptions.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Description clearly states the action (reject), the resource (pending join request), and the required parameters and role. It is specific and distinguishes from siblings like 'approve_join_request'.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly states the context (rejecting a request to join a community you run) and preconditions (must be admin/creator). It implies use case but does not explicitly mention when not to use or contrast with alternatives.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Many tools have overlapping purposes, particularly the generic create_production_item vs specific add_* tools (e.g., add_role, add_meal). This creates ambiguity, as agents may struggle to choose between generic and specific counterparts. Additionally, similar verbs like 'add', 'create', and 'bulk_create' blur boundaries.
Most tools follow a verb_noun pattern (add_guest, list_events), but there are inconsistencies: 'bulk_create_promo_codes' instead of 'create_bulk_promo_codes', mix of 'list' and 'get' (list_events vs get_account_status), and varied verbs like 'set', 'update', 'delete', 'archive', 'unarchive', 'reorder'. Overall pattern recognizable but not uniform.
115 tools is excessive for most domains, including event management. While the domain is complex, this granularity overwhelms agents and makes selection difficult. The tool count far exceeds typical well-scoped servers (3-15), indicating poor abstraction.
The tool set covers an extensive range of event management activities: events, tickets, guests, affiliates, discounts, production items, forms, communities, sponsors, and more. Minor gaps exist (e.g., no direct event deletion, only cancellation), but overall the surface is comprehensive for the stated purpose.