Skip to main content
Glama
abutbul

Gatherings MCP Server

by abutbul

rename_member

Update a participant's name in a social gathering to correct entries or reflect changes, using the gathering ID and both old and new names.

Instructions

Rename an unnamed member

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
gathering_idYesID of the gathering
old_nameYesCurrent name of the member
new_nameYesNew name for the member

Implementation Reference

  • MCP tool handler for 'rename_member': validates arguments using type guard and constructs/executes the Python CLI command 'rename-member' via child_process.exec.
    case 'rename_member':
      if (!isRenameMemberArgs(args)) {
        throw new McpError(ErrorCode.InvalidParams, 'Invalid rename_member arguments');
      }
      command += ` rename-member "${args.gathering_id}" "${args.old_name}" "${args.new_name}"`;
      break;
  • Input schema definition for the 'rename_member' tool, specifying properties and requirements for gathering_id, old_name, new_name.
    inputSchema: {
      type: 'object',
      properties: {
        gathering_id: {
          type: 'string',
          description: 'ID of the gathering',
        },
        old_name: {
          type: 'string',
          description: 'Current name of the member',
        },
        new_name: {
          type: 'string',
          description: 'New name for the member',
        },
      },
      required: ['gathering_id', 'old_name', 'new_name'],
    },
  • src/index.ts:140-161 (registration)
    Registration of the 'rename_member' tool in the ListTools response, including name, description, and input schema.
    {
      name: 'rename_member',
      description: 'Rename an unnamed member',
      inputSchema: {
        type: 'object',
        properties: {
          gathering_id: {
            type: 'string',
            description: 'ID of the gathering',
          },
          old_name: {
            type: 'string',
            description: 'Current name of the member',
          },
          new_name: {
            type: 'string',
            description: 'New name for the member',
          },
        },
        required: ['gathering_id', 'old_name', 'new_name'],
      },
    },
  • Type guard function for validating 'rename_member' tool arguments at runtime.
    const isRenameMemberArgs = (args: any): args is { gathering_id: string; old_name: string; new_name: string } =>
      typeof args === 'object' && args !== null &&
      typeof args.gathering_id === 'string' &&
      typeof args.old_name === 'string' &&
      typeof args.new_name === 'string';
  • CLI handler for 'rename-member' command, called by MCP server, invokes service.rename_member and formats JSON/text output.
    def handle_rename_member(service, args):
        """Handle the rename-member command."""
        try:
            member = service.rename_member(args.gathering_id, args.old_name, args.new_name)
            result = {
                "success": True,
                "member": {
                    "old_name": args.old_name,
                    "new_name": member.name
                }
            }
            if args.json:
                print(json.dumps(result))
            else:
                print(f"Renamed member from '{args.old_name}' to '{member.name}'")
            return True
        except ValueError as e:
            error = {"success": False, "error": str(e)}
            if args.json:
                print(json.dumps(error))
            else:
                print(f"Error: {e}")
            return False
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states the action is a rename operation, implying mutation, but doesn't cover permissions needed, whether changes are reversible, error conditions, or what happens on success. This is a significant gap for a mutation tool with zero annotation coverage.

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 a single, efficient sentence with zero waste. It's appropriately sized and front-loaded, directly stating the tool's purpose without unnecessary elaboration.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given this is a mutation tool with no annotations, no output schema, and 3 parameters, the description is incomplete. It doesn't explain behavioral aspects like side effects, return values, or error handling, leaving significant gaps for an AI agent to use 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?

Schema description coverage is 100%, so the schema already documents all three parameters (gathering_id, old_name, new_name). The description adds no additional meaning beyond what the schema provides, such as clarifying what 'unnamed member' means in relation to these parameters. Baseline 3 is appropriate when schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Rename an unnamed member' states the action (rename) and target (unnamed member), but is vague about what constitutes an 'unnamed member' and doesn't differentiate from sibling tools like 'add_member' or 'remove_member'. It provides basic purpose but lacks specificity about the resource context.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description offers no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., the member must exist and be unnamed), exclusions, or relationships to sibling tools like 'add_member' or 'remove_member'. Usage context is implied at best.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/abutbul/gatherings-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server