Reference: Agent Network Project Files

brokers:
  employee-onboarding-broker:     # The name that the agent (broker) will be referenced by. This value is used as the asset ID in Anypoint Exchange.
    card:
      protocolVersion: 0.3.0      # A2A protocol version that the broker supports.
      name: Employee Onboarding Broker
      description: This agent acts as a broker for employee onboarding. It orchestrates the onboarding process by leveraging available tools to ensure new employees have access to all of the required systems for their daily work.
      url: ${agentregistry.url}/employee-onboarding-broker   # URL where the broker is hosted. Represents the preferred endpoint as declared by the broker.
      provider:
        organization: MuleSoft
        url: https://www.mulesoft.com/
      defaultInputModes:         # Supported media types for input
        - application/json
        - text/plain
      defaultOutputModes:        # Supported media types for output
        - application/json
      skills:
        - id: onboarding-agent
          name: Onboarding Agent
          description: This agent acts as a broker. It orchestrates the use of specialized tools and agents (including MCP servers) to manage employee onboarding.
          examples:                # Usage examples
            - Onboard a new sales employee. Employee name is 'Alex Smith', email is 'alex.smith@example.com', and phone number is '555-123-4567'.
          inputModes:
            - application/json
            - text/plain
          outputModes:
            - application/json
            - text/plain
          tags: [onboarding]      # Categorization tags
      capabilities:
        streaming: false
        pushNotifications: false
        stateTransitionHistory: false
        extensions:
          - uri: "https://example.com/ext/konami-code/v1"
            description: "Description text"
            required: false
            params:
              hints: "Hint text"
      version: 1.0.0		          # Agent (broker) version

spec:
  llm:                            # LLM provider reference
  instructions:                   # Custom instructions
  maxNumberOfLoops: 25            # Max task steps (default: 25)
  maxConsecutiveErrors: 3         # Max recovery attempts
  tools: [...]                    # Available tools, including MCP servers
  links: [...]                    # Connected agents

  llm:                              # LLM provider reference
    ref:
      name: my-openAI               # Exchange asset ID of this LLM provider. By default, the groupId for this asset is the same as that in exchange.json.
      namespace:                    # Optional. If the asset was defined in a different business group, set the corresponding groupId here.
    configuration:
      model: gpt-5-mini

instructions:
- |
  You're an Employee Onboarding Broker. Coordinate onboarding of a new employee across the systems needed for day-to-day work.
  ## The process for onboarding an employee is:
  - Onboard in HR: Create the new employee record. Fetch the address using available tools. Don't ask for the address unless you're not sure how to get it.
  - Onboard in CRM: Create the employee's CRM profile.
  - Since this a long running task, send a Slack update using tool SlackMcpServer.send_status_update to communicate the status of actions taken so far. It should be a human-readable summary. For example: {
  {
  "message": "HR and CRM onboarding completed. Working on next steps...",
  "contextId": "<fetch-the-context-id-from-input>"
  }
  - Request employee laptop: Submit a laptop request in Zendesk.
  - Request employee badge: Initiate the employee badge request.
  - Send a Slack update using tool SlackMcpServer.send_status_update to communicate the status of actions taken so far. It should be a human-readable summary. For example: {
  {
  "message": "Zendesk laptop and badge onboarding completed. Working on next steps...",
  "contextId": "<fetch-the-context-id-from-input>"
  }
  - IT system setup: Provision the ping ID system for the employee.
  ## Final Response
  - Return a plain-text human-readable summary of all steps and actions taken, not just the final step. Format it in a bulleted list. DON'T include tool names in the summary.

     instructions:
        - |
          You're an Incident Management Broker. Your primary responsibility is to coordinate the resolution of incidents reported by customers.
          The process for incident management is:
            1. Fetch CRM case details: Retrieve the latest critical case details for the customer.
            2. Fetch entitlement details: Obtain the customer's entitlement information.
            3. Fetch on-call engineer: Identify the current on-call engineer for the incident.
            4. Create Slack war room and invite on-call engineer: Set up a Slack war room channel and invite the on-call engineer.
            5. Summarize actions: Provide a clear, human-readable summary of the steps performed, including information about the created Slack channel and the on-call engineer assigned.

links:
  - agent:
      ref:
        name: hr-agent        # Exchange asset ID of the linked agent. By default, the groupId for this asset is the same as that in exchange.json.
        namespace:            # Optional. If the asset was defined in a different business group, set the corresponding groupId here.
  - agent:
      ref:
        name: badging-agent
  - agent:
      ref:
        name: crm-agent
  - agent:
      ref:
        name: zendesk-agent
  - agent:
      ref:
      name: it-agent

tools:
  - mcp:
      ref:
        name: talent-pool-mcp         # Exchange asset ID of MCP server. By default, the groupId for this asset is the same as that in exchange.json.
      allowed:                        # Allowlist specific tools
        - TalentPoolMcpServer.match_email_to_address
  - mcp:
      ref:
        name: slack-mcp
      allowed:
        - SlackMcpServer.send_status_update

policies:
  - ref:
      name:          		# Exchange asset ID of the policy. By default, the groupId for this asset is the same as that in exchange.json.
      namespace:     		# Optional. If the policy was defined in a different business group, set the corresponding groupId here.
    configuration:
      policyConfig1: policyConfig1Value

      - agent:

           ref:

             name: weather-agent

           connection:

             ref:

               name: weather-agent-connection

      - agent:

           ref:

             name: weather-agent