Skip to main content
Glama
block

Square MCP Server

by block

team

Manage team operations including members, wages, labor schedules, and cash drawer shifts within Square's platform.

Instructions

Manage team operations

Args:
    operation: The operation to perform. Valid operations:
        Team Members:
            - create_team_member
            - bulk_create_team_members
            - update_team_member
            - retrieve_team_member
            - search_team_members
        Wages:
            - retrieve_wage_setting
            - update_wage_setting
        Labor:
            - create_break_type
            - create_shift
            - search_shifts
            - update_shift
            - create_workweek_config
        Cash Drawers:
            - list_cash_drawer_shifts
            - retrieve_cash_drawer_shift
    params: Dictionary of parameters for the specific operation

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
operationYes
paramsYes

Implementation Reference

  • The 'team' tool handler function, registered via @mcp.tool() decorator. It dispatches to various Square API team management operations based on the 'operation' parameter using a match statement.
    @mcp.tool()
    async def team(
        operation: str,
        params: Dict[str, Any]
    ) -> Dict[str, Any]:
        """Manage team operations
    
        Args:
            operation: The operation to perform. Valid operations:
                Team Members:
                    - create_team_member
                    - bulk_create_team_members
                    - update_team_member
                    - retrieve_team_member
                    - search_team_members
                Wages:
                    - retrieve_wage_setting
                    - update_wage_setting
                Labor:
                    - create_break_type
                    - create_shift
                    - search_shifts
                    - update_shift
                    - create_workweek_config
                Cash Drawers:
                    - list_cash_drawer_shifts
                    - retrieve_cash_drawer_shift
            params: Dictionary of parameters for the specific operation
        """
        try:
            match operation:
                # Team Members
                case "create_team_member":
                    result = square_client.team.create_team_member(params)
                case "bulk_create_team_members":
                    result = square_client.team.bulk_create_team_members(params)
                case "update_team_member":
                    result = square_client.team.update_team_member(**params)
                case "retrieve_team_member":
                    result = square_client.team.retrieve_team_member(**params)
                case "search_team_members":
                    result = square_client.team.search_team_members(params)
                # Wages
                case "retrieve_wage_setting":
                    result = square_client.labor.retrieve_wage_setting(**params)
                case "update_wage_setting":
                    result = square_client.labor.update_wage_setting(**params)
                # Labor
                case "create_break_type":
                    result = square_client.labor.create_break_type(params)
                case "create_shift":
                    result = square_client.labor.create_shift(params)
                case "search_shifts":
                    result = square_client.labor.search_shifts(params)
                case "update_shift":
                    result = square_client.labor.update_shift(**params)
                case "create_workweek_config":
                    result = square_client.labor.create_workweek_config(params)
                # Cash Drawers
                case "list_cash_drawer_shifts":
                    result = square_client.cash_drawers.list_cash_drawer_shifts(**params)
                case "retrieve_cash_drawer_shift":
                    result = square_client.cash_drawers.retrieve_cash_drawer_shift(**params)
                case _:
                    raise McpError(INVALID_PARAMS, ErrorData(message=f"Invalid operation: {operation}"))
    
            return result.body
        except Exception as e:
            raise McpError(INTERNAL_ERROR, ErrorData(message=str(e)))
  • The @mcp.tool() decorator registers the 'team' function as an MCP tool.
    @mcp.tool()
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 lists operation types but doesn't describe what these operations actually do behaviorally - whether they're read/write operations, what permissions are needed, what side effects occur, or how errors are handled. The description provides operation names but not their behavioral characteristics.

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 well-structured with clear categorization of operations and uses bullet points effectively. It's appropriately sized for a multi-operation tool, though the initial 'Manage team operations' line is somewhat redundant with the tool name. Each section earns its place by organizing the operation types logically.

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?

For a complex tool with 2 parameters, 0% schema coverage, no annotations, no output schema, and nested objects in parameters, the description is incomplete. While it documents operation values well, it doesn't explain the 'params' dictionary structure, return values, error conditions, or behavioral implications of different operations. This is inadequate for a multi-function mutation tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage and only 2 parameters, the description provides excellent semantic context for the 'operation' parameter by listing all valid operation values across four categories (Team Members, Wages, Labor, Cash Drawers). This significantly compensates for the schema's lack of documentation, though it doesn't explain the 'params' dictionary structure.

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 states 'Manage team operations' which provides a general purpose but is vague about what specific resources are managed. It distinguishes from siblings like 'bookings' or 'customers' by focusing on team-related functions, but doesn't specify the exact verb+resource combination clearly beyond the broad 'manage' term.

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?

No guidance is provided about when to use this tool versus alternatives. The description lists operations but doesn't explain context, prerequisites, or when specific operations should be chosen. There's no mention of when-not-to-use scenarios or how this tool relates to sibling tools like 'business' or 'customers'.

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/block/square-mcp'

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