mcp.json

{
  "$schema": "https://agent-plugins.org/schemas/1.0.0/mcp.schema.json",
  "mcpServers": {
    "perform-ai": {
      "type": "streamable-http",
      "url": "https://mcp.perform.ai/mcp-invoke",
      "extensions": {
        "com.openai": {
          "auth": {
            "type": "oauth"
          },
          "review": {
            "testCases": [
              {
                "description": "Use a dedicated reviewer account with access to MCP Demo Account (organization 7620). List available organizations and select that organization before organization-scoped queries. Fixtures must remain available. Compare carrier delays with pagination. Revalidate reviewer access and fixtures on the submitted production draft before submission. Inspect actual tool calls and arguments. Execute named methods through invoke_method_read with method and params. Use describe_methods for a named method when its input schema is unclear. Method names are not separate tool calls. These cases have not been run against the production invoke endpoint.",
                "userPrompt": "Which carriers had the most delayed deliveries to Germany in July 2026?",
                "toolsTriggered": "list_organizations, select_organization, invoke_method_read",
                "expectedOutput": "Use list_shipments_filters, get_shipment_filter_values and list_shipments through invoke_method_read. Use DELIVERED_DATE with July 1\u201331 2026 UTC, destination Germany and parcel.on_time_status_carrier=no, matching the live schema. Rank delayed deliveries by carrier from returned data. Follow pagination or disclose partial coverage. Never equate a page size with the total or repeat historic fixture counts."
              },
              {
                "description": "Use a dedicated reviewer account with access to MCP Demo Account (organization 7620). List available organizations and select that organization before organization-scoped queries. Fixtures must remain available. Inspect shipment history and identify the stall. Revalidate reviewer access and fixtures on the submitted production draft before submission. Inspect actual tool calls and arguments. Execute named methods through invoke_method_read with method and params. Use describe_methods for a named method when its input schema is unclear. Method names are not separate tool calls. These cases have not been run against the production invoke endpoint.",
                "userPrompt": "Walk me through everything that happened to shipment SHIP98941311 and tell me where it stalled.",
                "toolsTriggered": "list_organizations, select_organization, invoke_method_read",
                "expectedOutput": "Use get_shipment_details with shipment_id=SHIP98941311 and a projection including tracking events, matching the live schema through invoke_method_read. Present returned events chronologically, identify the longest observed stall and calculate its duration using timestamps. Distinguish observed events from inferred causes. Report a missing or inaccessible fixture explicitly rather than inventing a timeline."
              },
              {
                "description": "Use a dedicated reviewer account with access to MCP Demo Account (organization 7620). List available organizations and select that organization before organization-scoped queries. Fixtures must remain available. Cross-reference active configuration references with actual shipment usage. Revalidate reviewer access and fixtures on the submitted production draft before submission. Inspect actual tool calls and arguments. Execute named methods through invoke_method_read with method and params. Use describe_methods for a named method when its input schema is unclear. Method names are not separate tool calls. These cases have not been run against the production invoke endpoint.",
                "userPrompt": "Check our active carrier configs and flag any that are unused.",
                "toolsTriggered": "list_organizations, select_organization, invoke_method_read",
                "expectedOutput": "Use list_carrier_configs and get_shipment_filter_values through invoke_method_read. Request status=active, enumerate all configuration pages, and compare carrier reference and identity against shipment usage in an explicitly agreed date window. Preserve distinct configurations even when carrier names match. Report zero observed usage only for complete coverage; disclose truncation and do not label a configuration unused for all time."
              },
              {
                "description": "Use a dedicated reviewer account with access to MCP Demo Account (organization 7620). List available organizations and select that organization before organization-scoped queries. Fixtures must remain available. Rank year-to-date shipment volume. Revalidate reviewer access and fixtures on the submitted production draft before submission. Inspect actual tool calls and arguments. Execute named methods through invoke_method_read with method and params. Use describe_methods for a named method when its input schema is unclear. Method names are not separate tool calls. These cases have not been run against the production invoke endpoint.",
                "userPrompt": "What's our shipment volume by carrier this year?",
                "toolsTriggered": "list_organizations, select_organization, invoke_method_read",
                "expectedOutput": "Use list_shipments_filters and get_shipment_filter_values through invoke_method_read. Use carrier_name_carrier_reference with IMPORTED dates from January 1 of the current year through the run time, matching the live schema. State the date range, time zone and any truncation. Rank returned counts descending, retaining unidentified shipments. Derive totals from live results."
              },
              {
                "description": "Use a dedicated reviewer account with access to MCP Demo Account (organization 7620). List available organizations and select that organization before organization-scoped queries. Fixtures must remain available. Discover the current filter catalog. Revalidate reviewer access and fixtures on the submitted production draft before submission. Inspect actual tool calls and arguments. Execute named methods through invoke_method_read with method and params. Use describe_methods for a named method when its input schema is unclear. Method names are not separate tool calls. These cases have not been run against the production invoke endpoint.",
                "userPrompt": "What fields can I filter our shipments by?",
                "toolsTriggered": "list_organizations, select_organization, invoke_method_read",
                "expectedOutput": "Use list_shipments_filters through invoke_method_read. Organize the returned catalog by field name, display name and data type. Derive field counts from live results. Include filterability and grammar caveats and explain lifecycle date constraints separately. Do not invent fields."
              }
            ],
            "negativeTestCases": [
              {
                "description": "Generic drafting requires no account data. Do not invoke Perform.AI MCP tools or claim to send an email. Return a short generic draft without inventing shipment details.",
                "userPrompt": "Draft a short apology email to a customer whose order arrived late."
              },
              {
                "description": "General logistics knowledge does not require account data. Do not invoke Perform.AI MCP tools. Explain the general distinction or use authoritative public references; do not claim access to organization records.",
                "userPrompt": "What's the difference between DDP and DAP Incoterms, and which is better for a cross-border e-commerce provider?"
              },
              {
                "description": "Pickup creation is unsupported by the exposed MCP tool set. Explain that this connection cannot create a pickup, and do not claim a booking was made. Do not invoke Perform.AI shipment, booking-list, or configuration tools to perform or simulate creation.",
                "userPrompt": "Book a DHL Express pickup for tomorrow morning from our Berlin warehouse."
              }
            ]
          }
        }
      }
    }
  }
}